This repository has been archived by the owner on Feb 2, 2021. It is now read-only.
Setting REMOVE_VOLUMES=1 causes docker-gc to exit with status 1 #201
Labels
Comments
makkes
pushed a commit
to makkes/docker-gc
that referenced
this issue
Mar 26, 2019
This was referenced Mar 26, 2019
The main problem we have with this currently is that we call |
makkes
pushed a commit
to mesosphere-backup/docker-gc
that referenced
this issue
Mar 27, 2019
makkes
pushed a commit
to mesosphere-backup/docker-gc
that referenced
this issue
Apr 16, 2019
just for testing This reverts commit 15beb94.
makkes
pushed a commit
to mesosphere-backup/docker-gc
that referenced
this issue
Apr 16, 2019
This reverts commit e2bcad0.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@mattnworb @davidxia There's an open PR to fix this issue (#202) that is waiting to be merged. Would you be able to merge the PR or provide feedback, please? |
Sorry for the delay. I just merged it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When setting
REMOVE_VOLUMES=1
and there are no volumes found in Docker thendocker-gc
exits with status code 1 because ofgrep
returning 1 when it has not found any matches.How to reproduce
REMOVE_VOLUMES=1 docker-gc
What do you expect
docker-gc
should exit with status code 0.What happened instead
docker-gc
exits with status code 1.Software:
Full backtrace
The text was updated successfully, but these errors were encountered: