-
Notifications
You must be signed in to change notification settings - Fork 160
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
persistent data hint #62
Comments
Hi @dmnc-net Following the instructions in the quick start section will create a Docker volume and persist the Portainer data inside the volume. The instruction in the Persist Portainer data section simply shows an example on how to persist Portainer data via a bind mount. What could we change to make it clearer? |
I also got confused after reading the guide. I think it needs a little info when persiting via volume is enough and when persisting via a bind mount is better. |
Sorry for commenting on this, but to me it wasn't clear that the data was going to be persisted when created using the command in the quick start section. I found the persist section after I launched the container. By finding this I was certain that my data was going to still be there on a reboot. |
…sage of stack.env reference
Hi, I never worked with docker before so you may find me very confused, please be patient.
I'm running docker for testing/dev purposes on my Arch Linux laptop and I'm following the Portainer docs, so I did this:
Next, in the Persist Portainer data section I'm confused with "You’ll need to persist Portainer data to keep your changes after restart/upgrade of the Portainer container". But I don't want do a bind mount, I've created the volume which is located in
/var/lib/docker/volumes/portainer_data
. What do you mean by restart of the Portainer container? That means that docker will delete/recreate the volume every time when the service will be started/restarted (i.e. laptop reboot)? This makes on sense to me. Thanks for clarifyingThe text was updated successfully, but these errors were encountered: