-
-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build images through docker-compose #764
Comments
I've been having the same problem since last week (I think Friday) attempting to build with Buildkit 0.12.0 (running in Kubernetes pod) with the same setup running the same Docker server and runtime versions. Additional info: The error occurs for me at the point in a build when Buildkit attempts to execute the
Edit: Hopefully this is helpful in diagnosing, but I changed the Buildkit image to |
I also ran into this issue with with the docker buildx create \
--name fixed_builder \
--driver-opt 'image=moby/buildkit:v0.12.1-rootless' \
--bootstrap --use |
May I know how to set |
I just ran into this with a that being said, is there something lima/colima need to do to make the 'default' buildx work? or is this a bug in buildkit? just wondering if we've got the right path forward :) It may have to do with moby/buildkit#4003 |
Hey @onyxraven, any chance that you managed to set Colima's default buildx to set the rootless image? |
I haven't had a chance to dig, but at first glance it doesn't look like theres a config file that is referenced for this https://docs.docker.com/engine/reference/commandline/buildx_create/ -- at least that is obvious. It looks like there are some structures for a |
|
Same error here, using alpine images on M1Pro Macbook pro with buildx Doing this 👇 fixed the problem
|
For latest version v0.5.6, there is a new |
Just an FYI that this is getting fixed in the imminent v0.6.0 release. |
Description
Love colima but I very suddenly started having issues a few hours ago. My workflow relies on vscode dev containers to run a compose file that builds an image for the current codebase and runs containers for dependencies like an rdbms.
I didn't change anything about the codebase, dockerfile, images, compose file, colima configs, or docker configs to trigger this, but after doing many other re-builds I started getting this error on the first command after pulling the base image:
Steps I've tried are:
cgroup: private
andcgroup: host
to my compose fileMy current workaround is to build the image with
docker build
then use the image in the compose file as that seems to work fine.Version
Colima Version: 0.5.5
Lima Version: 0.17.0
Qemu Version: 8.0.3
Operating System
Output of
colima status
Reproduction Steps
docker-compose up
on a file that has a build section specifiedexample file:
Expected behaviour
build succeeds and containers start.
Additional context
Docker status dump:
lima info dump:
The text was updated successfully, but these errors were encountered: