-
Notifications
You must be signed in to change notification settings - Fork 390
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
[Question]: Recreate container without dataloss #894
Comments
Normally this should not happen. But maybe you have some setting enabled that automaticly removes volumes after stopping? In any case you can use a normal directory instead of a volume: volumes:
- /var/dsm:/storage That way you can see all the files and make sure they are not deleted after stopping. |
I did not change the path, this is what is in my compose up file: services:
dsm:
container_name: dsm
image: vdsm/virtual-dsm
environment:
DISK_SIZE: "2000G"
DISK_FMT: "qcow2"
RAM_SIZE: "32G"
CPU_CORES: "10"
devices:
- /dev/kvm
- /dev/net/tun
cap_add:
- NET_ADMIN
ports:
- 5000:5000
- 5001:5001
volumes:
- /var/dsm:/storage
restart: always
stop_grace_period: 2m So I was very confused that after I changed something and did a compose up, the container started as a fresh install I had to give a name to the device and set a username and password and everything was gone. |
Yes it might have something to do with Unraid, I think the path There is a community app called |
Great, I have installed that one! Somehow missed it :) Thanks for the quick response! |
Is your question not already answered in the FAQ?
Is this a general question and not a technical issue?
Question
I have a question, I started testing the container and uploaded data to it. When I change a parameter in the compose file and do a compose up, the container is recreated and all data is lost.
Is there a way to keep the data when the container is recreated?
The text was updated successfully, but these errors were encountered: