-
Notifications
You must be signed in to change notification settings - Fork 90
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
errors with 'docker-clean all' command #20
Comments
Do you only see these errors on the |
@killianbrackey no error on |
I have a similar errors but the images are actually cleaned from my hard drive.
|
Also, would be nice to have a clear tag usage for each specific docker version. I see that not all image working. I had to try 3 of them. |
@pascalandy thanks for the update. It looks like the bash array isn't updated when values are being removed. I will take a look at this in the next couple of days. The automated builds are not working (switched from automated build to makefile for multiple image builds). However the tags in DockerHub are here: https://hub.docker.com/r/zzrot/docker-clean/tags/ Which of the tags did you notice wasn't working? Also I agree that the tagging could be better -- it is currently ad hoc based on requests for older docker versions |
Tag 2.0.4 is not working |
…er-clean version mention #20
Added a tag for the version of docker clean @pascalandy. I will add an overhaul of the tagging system to the roadmap list @Skilgarriff and I are putting together. Added a link to the tags in the README.md as well |
I think the error I'm getting here are related to this issue:
Also, could you please get rid of the exclamation marks in the messages ? They're embarrassing... |
new weird messages popping up while using
|
1. What version of Docker-Clean are you running ?
2.0.4
2. What command are you trying to run?
docker-clean all
4. What did you see instead ( 'docker-clean -l or --verbose' for the entire log )?
5. What are your system specs?
Docker Version: 1.11.2, build b9f10c9
OS/Version: Ubuntu 14.04
The text was updated successfully, but these errors were encountered: