fix: Better support distrobox (#160)
We will now have a dedicated alpine based `distrobox` image. Due to restrictions in how the `/tmp` directory in a `distrobox` image works, it will not play nicely with generating a local tarball for rebasing a locally built image. Going further into fixing this would required a rootful setup and I'd rather leave the `distrobox` method as an easy way to try out building a recipe for users who are not booted on a `bluebuild` image. Extra packages are installed to make the `distrobox` setup quicker and a `distrobox.ini` file is provided to easily create the container and export the CLI for use on the host machine. The `podman` binary is passed into the `distrobox` container so that all images that are built will be accessible locally and allows rootless operation without extra setup.
This commit is contained in:
parent
0de0417515
commit
367359e8ea
7 changed files with 83 additions and 90 deletions
|
|
@ -125,8 +125,7 @@ init:
|
|||
--no-git
|
||||
|
||||
legacy-base:
|
||||
FROM ../+blue-build-cli-alpine --RELEASE=false
|
||||
RUN apk update --no-cache && apk add bash grep jq sudo coreutils
|
||||
FROM ../+blue-build-cli --RELEASE=false
|
||||
ENV BB_TEST_LOCAL_IMAGE=/etc/bluebuild/cli_test-legacy.tar.gz
|
||||
ENV CLICOLOR_FORCE=1
|
||||
|
||||
|
|
@ -140,9 +139,8 @@ legacy-base:
|
|||
DO +GEN_KEYPAIR
|
||||
|
||||
test-base:
|
||||
FROM ../+blue-build-cli-alpine --RELEASE=false
|
||||
RUN apk update --no-cache && apk add bash grep jq sudo coreutils git && \
|
||||
git config --global user.email "you@example.com" && \
|
||||
FROM ../+blue-build-cli --RELEASE=false
|
||||
RUN git config --global user.email "you@example.com" && \
|
||||
git config --global user.name "Your Name"
|
||||
|
||||
ENV BB_TEST_LOCAL_IMAGE=/etc/bluebuild/cli_test.tar.gz
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue