Skip to content
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

Remove repositories #148

Closed
creack opened this issue Mar 24, 2013 · 4 comments
Closed

Remove repositories #148

creack opened this issue Mar 24, 2013 · 4 comments
Milestone

Comments

@creack
Copy link
Contributor

creack commented Mar 24, 2013

We need to be able to remove repositories/tags.

@ghost ghost assigned creack Mar 24, 2013
@creack
Copy link
Contributor Author

creack commented Mar 24, 2013

I start by adding the command 'rmrep' and I'll merge all the 'rm' later.

@shin-
Copy link
Contributor

shin- commented Mar 25, 2013

The changeset you're attaching has this comment in the commands.go file: // Priority: Container, Image, Repository

My concerns with this are two-fold:

  1. While this is documented in the source-code, there is nothing to indicate it in the UI, which is bound to be confusing for users
  2. Isn't this a recipe for disaster? Like - how much can I trust this order to stay consistent in future updates? Can I use it in my docker scripts without fear that tomorrow's update will break the state of my docker?

As a side note, it also seems that I could mistype rm while trying for rmi or rmc and end up with unexpected results (but I guess the same argument could be made for rmi versus rm before).

Just my two cents!

@creack
Copy link
Contributor Author

creack commented Mar 25, 2013

Ok for the UI, but the thing is that containers, images and reporisotires have different formats, so if you try to rmc an image or rmi a container, it will just fail :)

@creack
Copy link
Contributor Author

creack commented Apr 12, 2013

Fixed by #385

@creack creack closed this as completed Apr 12, 2013
runcom pushed a commit to runcom/docker that referenced this issue May 4, 2016
Bug 1300076 - SIGPIPE events kill go process
dperny pushed a commit to dperny/docker that referenced this issue Oct 18, 2021
[master] Do not add EE specific security labels to daemon store each time Info retrieved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants