-
Notifications
You must be signed in to change notification settings - Fork 74
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
crashplan must re-adopt machine every time docker container is started #41
Comments
You shouldn't map any volumes to /var/lib/crashplan. The container create a symlink there, and stores the identity on /config/id ' |
Thanks. I’ll try that. Do you know of any way to keep the daemon from changing the .ui_info file each time it starts?
|
No, I tried and failed there. |
Bummer. Thanks.
|
FWIW I'm having the same issue with my own crashplan Dockerfile. Haven't solved it yet. Would love a solution. |
@bennytheshap Try using this line (with the :rw when starting the container:
|
Having the same issue, and my config directory is mounted RW on host storage. |
+1 |
No matter what I try, crashplan gets logged out every time I re-start it via docker.
This is reflected in an error message in the client that says "Logged out by authority - Invalid application state" (see screenshot).
Am I doing something wrong?
I am starting docker with the following command line:
docker run -h ${HOSTNAME} --name=crashplan -v /mnt/ssd/storage/crashplan/config:/config -v /mnt/ssd/storage/crashplan/var/lib/crashplan:/var/lib/crashplan -v /mnt/biggun:/data -v /etc/localtime:/etc/localtime:ro -p 4242:4242 -p 4243:4243 gfjardim/crashplan
The text was updated successfully, but these errors were encountered: