-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
build
fails on component non-zero exit code when docker build
does not
#1554
Comments
I believe you are mistaken: Dockerfile
Looks like docker build also exits as soon as it hits a failure. |
Hmm, I can't get this to re-occur now after doing an upgrade to 1.3.0 RC3. It could have been an edge case between versions. I'll reopen if it pops up again. |
For anyone encountering this, it appears to be a race condition when running out of memory on the host. |
@timfallmk Ah, thanks !!! |
This error can also be recreated by removing a container from the Kitematic interface during a build. |
Thank you, @timfallmk! That solved the problem for me 😄 |
+1 when low on memory |
This also happens when renaming a container within Kitematic during a build. |
I got the same error while running out of disk space during a build. |
Bumping up my droplet's RAM from 512MB to 2GB fixed it as well. |
Clear your Cache, it helped me. https://net2.com/how-to-clean-up-unused-docker-containers-images-and-volumes/ |
hello i faced this problem during install xraygen on my vps ubuntu 20.04 lxd how i can fix it ? |
Running
docker-compose build --no-cache
will fail if one of the Dockerfile commands returns a non-zero exit code. However runningdocker build --no-cache
will return successfully in the same condition.Example:
Dockerfile has command
RUN npm install libxmljs
:npm
will returncode 137
(a warning) from this commanddocker-compose
will exit at this stage whiledocker
does not.I can provide more details of the builds if necessary.
The text was updated successfully, but these errors were encountered: