From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] scripts: add container.sh as simple podman wrapper
Date: Tue, 13 Jun 2023 10:44:16 +0200 [thread overview]
Message-ID: <20230613084416.GR18491@pengutronix.de> (raw)
In-Reply-To: <20230612065626.387660-1-ahmad@a3f.at>
On Mon, Jun 12, 2023 at 08:56:26AM +0200, Ahmad Fatoum wrote:
> We have a Containerfile in tree now that is used for CI, but it's not
> completely self evident, how to use it locally. Add a simple script
> that mounts the current working directory into the container and calls
> its arguments inside.
>
> Example building MAKEALL (Some configs will expectedly fail due to size
> or firmware constraints):
>
> ./scripts/container.sh ./MAKEALL
>
> Example starting a shell:
>
> ./scripts/container.sh /bin/bash
>
> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
> ---
> scripts/container.sh | 39 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100755 scripts/container.sh
Applied, thanks
Sascha
>
> diff --git a/scripts/container.sh b/scripts/container.sh
> new file mode 100755
> index 000000000000..4ddee7d0a90c
> --- /dev/null
> +++ b/scripts/container.sh
> @@ -0,0 +1,39 @@
> +#!/bin/sh
> +# SPDX-License-Identifier: GPL-2.0-only
> +
> +CONTAINER=${CONTAINER:-ghcr.io/barebox/barebox/barebox-ci:latest}
> +KCONFIG_ADD="$test/kconfig/disable_target_tools.kconf KCONFIG_ADD"
> +
> +while getopts "c:uh" opt; do
> + case "$opt" in
> + h)
> + echo "usage: $0 [-c CONTAINER] [command...]"
> + echo "This script mounts the working directory into a container"
> + echo "and runs the specified command inside or /bin/bash if no"
> + echo "command was specified."
> + echo "OPTIONS:"
> + echo " -c <container> container image to use (default: $CONTAINER)"
> + echo " -u pull container image updates"
> + echo " -h This help text"
> +
> + exit 0
> + ;;
> + u)
> + update=1
> + ;;
> + c)
> + CONTAINER="$OPTARG"
> + ;;
> + esac
> +done
> +
> +shift $((OPTIND-1))
> +
> +[ -n "$update" ] && podman pull "$CONTAINER"
> +
> +pwd_real=$(realpath $PWD)
> +
> +exec podman run -it -v "$PWD:$PWD:z" -v "$pwd_real:$pwd_real:z" --rm \
> + -e TERM -e ARCH -e CONFIG -e JOBS -e LOGDIR -e REGEX \
> + -e KCONFIG_ADD -w "$PWD" --userns=keep-id \
> + -- "$CONTAINER" "${@:-/bin/bash}"
> --
> 2.40.1
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-06-13 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 6:56 Ahmad Fatoum
2023-06-12 7:01 ` [PATCH] fixup! " Ahmad Fatoum
2023-06-13 8:44 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230613084416.GR18491@pengutronix.de \
--to=sha@pengutronix.de \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox