Currently the only way that I know that works is to stop the container, then delete the container and create a new one....

This seems completely bonkers…

Surely there is a “proper” way to do the following:

1. docker run -d –name some-ghost ghost
2. gah! forgot to expose ports
3. docker stop some-ghost
4. docker rm some-ghost
5. docker run -d –name some-ghost -p 8080:2368 ghost
6. oh shit i just deleted all my posts… oh right, use a data container
7. docker stop some-ghost
8. docker rm some-ghost
9. docker create -v /var/lib/ghost –name some-data busybox
10. docker run -d –name some-ghost -p 8080:2368 –volume-from some-data ghost
11. awesome, its up, now lets see what happens when i restart the host, hmm it didn’t start, oh i need to add a restart policy
12. docker stop some-ghost
13. docker rm some-ghost
14. docker run -d –name some-ghost -p 8080:2368 –volume-from some-data –restart unless-stopped ghost
15. profit!!

It is not obvious to me, seems like you need to know what you’re doing 100% up front before you even think about issuing a docker run or create command, if you forget an option you need to start again… Surely there is a modify options for container command or something?