Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Squashing an image that is already squashed causes a nonzero exit code
See original GitHub issueWe’ve integrated docker-squash into our pipeline for certain Docker images. If an image has already been squashed, though, docker-squash exits with an exit code of 0, which indicates an error.
It would be nice if this particular situation wasn’t considered an error, or at least offer a command-line flag that would print a message to the INFO or WARNING logger but not exit 1.
A workaround for this problem would be to skip error checking for this part of our pipeline.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you, I’ll change this to warning and exit gracefully.
Sounds good. +1