genuinetools / img

Standalone, daemon-less, unprivileged Dockerfile and OCI compatible container image builder.
https://blog.jessfraz.com/post/building-container-images-securely-on-kubernetes/
MIT License
3.88k stars 230 forks source link

img build with `overlayfs` option fails #296

Open rohinb2 opened 4 years ago

rohinb2 commented 4 years ago

Running default container (r.j3ss.co/img) with following args: ...--name img --security-opt seccomp=unconfined --security-opt apparmor=unconfined <image-name> --privileged.

Running img command like so: img build -b overlayfs -t test -f <Dockerfile-path>.

After FROM ... step completes, get the following error: Error: failed to solve: failed to mount /run/user/1000/containerd-mount629896361: operation not permitted.

I am attempting to use overlayfs because I'm getting a similar issue to https://github.com/moby/buildkit/issues/1279 when using auto. Many operations become extremely slow after some copies are executed in the Dockerfile provided to img. Alternatively, if there is a solution to this problem that can be helpful as well!

I've looked through a lot of the documentation/issues, can't seem to find anything super similar.

issue-label-bot[bot] commented 4 years ago

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.71. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

rohinb2 commented 4 years ago

@AkihiroSuda Perhaps you could provide some clarity on this? We looked at issues: https://github.com/containerd/containerd/issues/2246, https://github.com/containerd/containerd/blob/master/docs/rootless.md.

I've even tried running the container with USER root added into the Dockerfile, but then I get an error as follows: Error: failed to solve: failed to convert whiteout file "etc/alternatives/.wh.pager.1.gz": operation not permitted.

I see you addressed a similar issue here: https://github.com/containerd/containerd/issues/3762, but that seems to be in rootless mode where as in this case I am running with root and with --privileged. Thanks for any help!

Asciotti commented 3 years ago

Any updates on this? Thanks!

rohinb2 commented 3 years ago

Any updates on this? Thanks!

Ended up just using buildkit directly. img is not maintained as actively AFAIK and is more of a proof of concept.