- Buildah - Podman List Archives

Podman, Buildah, and Podman Desktop Mailing List Upgrade and Downtime (try two, with the right list addresses for Buildah and Podman Desktop)
by Tom Sweeney 30 Sep '26

30 Sep '26

-------- Forwarded Message -------- Subject: Podman, Buildah, and Podman Desktop Mailing List Upgrade and Downtime Date: Wed, 30 Sep 2026 11:36:06 -0400 From: Tom Sweeney <tom.sweeney(a)redhat.com> To: podman(a)lists.podman.io, buildah(a)list.podman.io, Podman-desktop(a)list.podman.io Hi Folks, On Sunday October 4, 2026 at 9:30 pm EDT (UTC-4), the Podman related mailing lists will be going down for a few hours in order to do an upgrade. During that time, emails will likely be returned to the sender, or possibly drop somewhere into the ether in CyberSpace. The upgrade should take under 4 hours, and we plan to have the system back around 1:30 am EDT on Monday October 5, 2026. After the upgrade, you should not notice any difference in the list when interacting with it via your favorite email interface. If you use the web interface for the list at: https://lists.podman.io/, you will see some changes there, and there should be some nice improvements for administration tasks on the site. NOTE: If you use Fedora Authorization to log into the web interface, you will not be able to log in via that. You'll need to use the lost password mechanism to set up a new password. From what we can see, only 5 people have used Fedora to authenticate to that list in the past year, so we hope this will be a minimal disruption. Regards, t

1 0

Skip tarball generation for layers when building a container image
by Dick Marinus 27 Sep '26

27 Sep '26

Hi! Last month I started the following topic at github discussions but I didn't receive any replies. https://github.com/podman-container-tools/buildah/discussions/7060 So I'm trying again here, I hope someone responds. I'm using buildah to build large (20GB) images, I'm not interested in pushing the image to a registry because I'm using it to build a squashfs image from the contents. I like the intermediate layers when building an image which allow me to restart at a failing step (skipping all steps that completed successfully). But as the image increases in size during build, the layers grow as well and a tarball is generated for every layer in $TMPDIR which requires a lot of disk space, wasted time and wear on my SSD. Currently I'm working around this by using a shell script instead of a Containerfile which uses the following shell script: ```bash #!/bin/bash set -eux SRC=$1 DST=$2 buildah from --name=$DST scratch buildah unshare << @EOF set -eu SRC_MOUNT=\$(buildah mount $SRC) DST_MOUNT=\$(buildah mount $DST) shopt -s dotglob cp --reflink=always -rp \${SRC_MOUNT}/* \${DST_MOUNT}/ @EOF ``` To create a reflinked clone of a buildah container. But this only works on btrfs (and zfs?). This leads me to two questions: 1. Would it be possible to disable this tarball generation when using a Containerfile, with the side note that the generated image cannot be pushed? 1. Would it be a good idea to add a `buildah clone` command for this? There's already `podman clone` but that creates a new container from the source image discarding all changes from the source container.

1 0

Collaboration Request for Tuskegee Data Center
by Miles Ingram 06 May '25

06 May '25

Dear Buildah Team, I hope this message finds you well. I am writing to explore the possibility of collaborating with your team on a project at the Tuskegee Data Center. We are considering Red Hat OpenShift as a more cost-effective and efficient solution for our AI and data management needs. Red Hat OpenShift offers a comprehensive platform for managing AI models and applications, with built-in AI capabilities. It supports various AI/ML tools and provides flexibility across hybrid cloud environments. Additionally, it simplifies resource provisioning and automates many tasks, which can reduce operational complexity and costs. We believe that leveraging OpenShift could significantly enhance our operations and are keen to learn more about how we can transition to this platform. Your expertise and insights would be invaluable in this process. Would you be available for a meeting to discuss this potential collaboration in more detail? We are eager to understand how we can best utilize OpenShift with Docker for our project and any support your team can provide. Thank you for considering this request. I look forward to your positive response. Best Regards, Miles C. Ingram Co-Founder, Vice President Dystopia, Dystopian Space M.INGRAM(a)DYSTOPIACONSULTING.COM 251.257.6231 [cid:ac349e83-51a5-4320-9ed4-c873bd5da182]

1 0

DevConf.US 2024 CfP Now Open!
by Tom Sweeney 27 Mar '24

27 Mar '24

Hi Everyone, We are excited to announce that the 6th annual DevConf.US CfP <https://pretalx.com/devconf-us-2024/cfp>[1] is currently open! Head to DevConf.US <http://devconf.us>[2] to submit your talks, workshops, and discussion abstracts, along with meet-ups, BoF's, community booth proposals and really, anything else you are excited to share with the community! Checkout the website <http://devconf.us>[2] for more details and topics that we are looking for this year. The conference will be held from August 14th to 16th 2024 at Boston University in Boston, MA. We can’t wait to see you there! Note: The deadline for submissions is April 8, 2024. Help us get the word out on social media: * Follow @devconf_usand retweet all the tweets! * Follow us on instagram @devconf_usand share our posts! * Follow us on LinkedIn: https://www.linkedin.com/company/devconf-us/ <https://www.linkedin.com/company/devconf-us/> * Or tag us in your posts and tweets and we will republish! Please send questions, comments, and concerns to info(a)devconf.us <mailto:info@devconf.us>. Looking forward to all your awesome proposals! Best regards, The DevConf.US Crew @DevConf_US #definefuture [1]: https://pretalx.com/devconf-us-2024/cfp <https://pretalx.com/devconf-us-2024/cfp> [2]: http://devconf.us <http://devconf.us>

1 0

Buildah Mulit-Arch Builds
by Ron Bernard 04 May '23

04 May '23

Hello, Is it possible to do buildah builds within a container as a non-root user and without the –privileged option? I’ve made several attempts and keep getting format exec errors when trying to do RUN commands that are in my Dockerfile. Could really use some guidance on how to achieve this. Thanks, Ron Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

Buildah v1.30 has arrived!
by Tom Sweeney 21 Apr '23

21 Apr '23

Hi All, Buildah v1.30 has recently dropped and it has a number of bug fixes and improvement. In particular, build argument handling has been made more intuitive and the `--network` option now works in the RUN command in a Containerfile. Check out the Release Announcement on Buildah.io! (https://buildah.io/releases/2023/04/21/Buildah-version-v1.30.0.html) t

1 0

'overlay' is not supported over overlayfs
by Sopena Ballesteros Manuel 21 Feb '22

21 Feb '22

Dear buildah community, we are just trying to create a container image inside an unprivileged container using buildah, however this process fails as shown below: $ buildah bud -f Dockerfile --format docker -t $IMAGE_NAME 'overlay' is not supported over overlayfs, a mount_program is required: backing file system is unsupported for this graph driver any idea what we are doing wrong? thank you

2 1

Commit Multiarch images
by aflom＠redhat.com 01 Oct '21

01 Oct '21

I'm importing buildah into an application and I don't see a good way to commit multiarch images with github.com/containers/buildah/commit.go/Commit. I see that define.BuildOpts has a platform that is slice of structs that is used for building multi-arch images. The only architecture selection that i see for Commit, is a SystemContext.ArchitectureChoice, which is a single string. Do I have to use bud for multi-arch builds or is there a streamlined way to use Commit?

3 8

Buildah image size
by Michael Ivanov 10 Sep '21

10 Sep '21

Hallo, I am building a rootless image using buildah from some base image. The resulting image size as shown by podman images is about 1.3Gb. When I run the image container size reported by podman inspect --size is also approximately the same. podman image tree shows 3 layers for this image and the sum of space, reported for all layers also matches image size. But when I run du -sh / inside the container, the size reported is just about 800Mb. Where the extra 0.5Gb has disappeared? While building the image I delete a lot of files from base image: can it be that even when the files are removed the space, used by them is not actually released? Best regards, -- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans(a)isle.spb.ru | ^ ^ | |

4 4

Buildah's GitHub upstream branch has been renamed!
by Tom Sweeney 30 Jun '21

30 Jun '21

Hi All, 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. Best Wishes, t

1 0