Daniel J Walsh

This is being worked on in https://github.com/containers/ramalama/pull/1807

LGTM

Are you running within a container? If yes then the container is running without the UNSHARE syscall do to seccomp. Potential other reason would be you are on a system...

Bottom line Buildah inside of a container needs CAP_SYS_ADMIN or CAP_SETUID and CAP_SETGID to unshare user namespace and mount file systems. From a SECCOMP point of view it needs the...

@nalind has started working on designing rechunking into buildah. And has some preliminary code for it. Thoughts on actual how you would rechunk is still being discussed.

Let's just add the ones that make no sense to unshare to the line above: switch cmd.Use { case "", "help", "version", "mount": return nil }

@flouthoc PTAL

In order to mount a file system you either need to have CAP_SYS_ADMIN or you need to be able to create a user namespace which requires CAP_SETUID, CAP_SETGID. Nothing else...

This is actually a mistake. I did update the version in the X86_64, I believe. Can not check right now, since I am on plane. MAC Version might not have...

The way I did it on X86 was to update version, build images and then release. But this is definitely a chicken and egg.