Saving credentials, part II

Thanks very much for this useful image. One problem I have is I want to deploy it into my private repository already logged in. To do this I tried removing the volume you have created at ```/dbox/.dropbox```. This way I can commit that directory's contents back to the image after running it and logging it in.

Doing so, I can clearly see the ```/dbox/.dropbox``` contents in my ```docker diff``` output, before ```docker container commit```ing them. But after I stop the container and start my newly committed image, it requires logging in with the URL again.

The files are there, but the running Dropbox service seems to reject them. What am I missing?

-Brandon

Start by reproducing the workflow involving /dbox/.dropbox, docker diff, and docker container commit. Inspect how the Dropbox service uses the committed credentials when the newly committed image starts. Done means the image starts without requiring the login URL again, or the limitation is documented.

Written by the indexing model from the issue text.