We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
podman-machine rm default
DO NOT USE same machine name created by docker-machine
docker-machine
I have a boot2docker machine using docker-machine create default created before.
docker-machine create default
then I use podman-machine create default.
podman-machine create default
After podman-machine rm default, it would delete docker-machine named default instead without any warnings or check.
default
The text was updated successfully, but these errors were encountered:
There is no namespacing of VMs, so everything will be shared in e.g. VirtualBox.
The current workaround was to not use the name "default", but call it "box" instead.
You should have gotten a question though, before it removed the (docker) machine ?
$ podman-machine rm default About to remove default WARNING: This action will delete both local reference and remote instance. Are you sure? (y/n):
Sorry, something went wrong.
Yes, I got it.
There was two VMs named default before. So I made this mistake. It removed the first one it met.
Did something need changing ?
Or is it enough with a big warning
Warning e.g. This action will delete both local reference and remote instance, including your docker-machine as well !!
This action will delete both local reference and remote instance, including your docker-machine as well !!
No branches or pull requests
DO NOT USE same machine name created by
docker-machine
I have a boot2docker machine using
docker-machine create default
created before.then I use
podman-machine create default
.After
podman-machine rm default
, it would delete docker-machine nameddefault
instead without any warnings or check.The text was updated successfully, but these errors were encountered: