Just a quick note aimed mostly towards our contributors. The 'master'
branch on the Buildah GitHub Repository
(https://github.com/containers/buildah) has been renamed to 'main'. If
you have a local clone of the repository, then you should do the following:
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
Then the hardest part will then be retraining the muscle memory in your
fingers to type main now! FWIW, the Podman and Skopeo projects, along
with most of the other projects in the the Containers organization on
GitHub have also been changed.
Not sure if this is a buildah issue or perhaps a Tekton/OpenShift Pipelines
(which is driving my image build).
I have a multi-stage Dockerfile that is used in my pipeline's buildah bud
execution. Every time this runs, it fails at the first COPY step in the
"COPY --from=compile --chown=1001:0 /work/shared /opt/ol/wlp/usr/shared/"
The failure is:
STEP 8: COPY --from=compile --chown=1001:0 /work/shared
error building at STEP "COPY --from=compile --chown=1001:0 /work/shared
/opt/ol/wlp/usr/shared/": error adding sources
no items matching glob
copied (1 filtered out): no such file or directory
level=error msg="exit status 125"
This is the command being used to run the build:
buildah --storage-driver=vfs bud
--tls-verify=false --no-cache -f ./Dockerfile -t
The Dockerfile builds fine with Docker, so I'm assuming I'm either missing
some buildah bud option to allow for this behavior, or perhaps there is an
issue with my file system in my pipeline in OCP....
Thanks for any help!
Buildah v1.21.0 is now available and we've just posted the Release
Announcement with the details at:
There's now a new --secret option for the bud command that let's
you insert "secret" info into your container image such as a database
password, yet not have it visible to anyone within the container. Also
the "buildah manifest rm" command has been added to allow you to remove
one ore more manifests from an image, and a lot of work under the covers
to make the image operations faster and the code usable across the
container projects. Plus a number of smaller fixes and improvements
Thanks to the many contributors for their help and contributions!
This is my first time posting to a mailing list so if I do something uncouth please do let me know!
Podman has podman-remote with the ability to connect to a remote host which is useful for those on Macintosh and Windows systems to make use of podman.
Something similar for Buildah would be nice as well but from what I've seen in GitHub issues related to the topic, such a feature isn't planned which leads me to my question: are there no plans for something like a buildah-remote utility because it's not a priority/concern or because it's architecturally difficult to do even if it was a priority?
If such a thing as buildah-remote would be possible, would there be any concerns around submitting patches? It seems like it would be kind of a big change if it were to be added by a third party so I'm not sure if the Buildah project would be eager for such contributions.
This isn't a feature request, I'm not here to demand that anyone start building this for me if it's possible so don't worry about that.