-
Notifications
You must be signed in to change notification settings - Fork 606
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
nerdctl compose removes containers on termination (stop vs down) #666
Comments
|
I definitely second that. Fair to mention though that |
I think this proposal is making sense. I will make a try to impl it. cc @AkihiroSuda would you mind assigning this issue to me? |
Any news about this 'stop' command implementation ? :) |
Working on it now,maybe this feature can be released in v0.23.0 |
+1 Maintaining volumes is a really important feature; thank you for the great work! |
@Zheaoli are you still working on this? Otherwise I'd like to give it a try. |
@djdongjin Sure you can make a try |
I use nerdctl in a
lima
vm on mac as a replacement fordocker-compose
.docker compose
(ordocker-compose
) supports astop
command. It retains the created containers by just stopping them. In oppose to that, thedown
command removes the containers after stopping.nerdctl
only has thedown
command.When I run
nerdctl up
and ctrl-c the process, this is effectively adown
and the containers are removed.One can reproduce this with a simple
docker-compose.yml
file:With the original
docker-compose
the stopped containers are still present:Proposal:
nerdctl compose stop
command (and probablystart
?)ctrl-c
signal listener innerdctl compose up
trigger the stop command instead of down.The text was updated successfully, but these errors were encountered: