#Issues with non-Docker runtimes

1 messages · Page 1 of 1 (latest)

turbid hedge
#

Specifically this is what i'm seeing. Works when I use Docker

Stdout:
invoke: input: container.publish resolve: failed to solve for container publish: process "/dev/.buildkit_qemu_emulator update-ca-certificates" did not complete successfully: failed to copy xattrs: failed to set xattr "security.selinux" on /tmp/buildkit-qemu-emulator2896312290/dev/.buildkit_qemu_emulator: operation not supported
atomic badger
#

I ran into some different issues using podman on Linux in the past with commands that worked in Docker but not in Podman.

#

What filesystem are you using on MacOS in the docker VM? The error that your gettting is that xattrs are not supported which is how Linux stores posix acl (when basic posix permissions are too simple) and RBAC controls like selinux and app armor.

turbid hedge
#

The same works with Docker though. I haven't made any custom changes to docker. It's what comes ootb.

turbid hedge
#

The filesystem used by docker is overlayfs2 but with podman its xfs.

#

According to the issue linked above, it's an issue with buildx. How does that come into play within the dagger engine though? The engine buildkit version is the same. I am far from an expert in this area though. My goal is to have to inform my dagger users consistently on how to utilize it. I don't want them to have to do custom docker/podman engine shenanigans to get going. I am planning on trying some other tools like nerdctl also.