5 ms·
This makes it sound like it's quite common to use docker containers operating in a heavily stateful fashion. Is that indeed common nowadays? (Though, the state
by stcredzero 7y ago
This makes it sound like it's quite common to use docker containers operating in a heavily stateful fashion. Is that indeed common nowadays? (Though, the state in this case is only counted on to persist in the named volumes.)
- sz4kerto 7y agoThat's completely fine given that the important state is on volumes (named, persistent, bind mounted, whatever).
- johnchristopher 7y agoWell, you are supposed to be able to delete all your volumes, containers and networks and then regenerate it by running the recettes (edit:I mean.. recipes :D) (Dockerfile, docker-compose, kubernetes, volume backup, etc.).
- stcredzero 7y agoWell, you are supposed to be able to delete all your volumes, containers and networks and then regenerate So then Docker is designed to treat all of those as disposable. I just searched "recette" and only came up with French cooking references.
- ashtonbaker 7y ago> I just searched "recette" and only came up with French cooking references. Perhaps a phonetic spelling of "resets" by a French person :)
- johnchristopher 7y agoSomething like that :D. I was thinking "recette" as in "recipe" but somehow only the word "receipt" came to my mind so I thought "oh, it must be one of those words that are the same in both language". I am a bit tired.
- dunham 7y agoIt's french for "recipe".
- johnchristopher 7y ago> So then Docker is designed to treat all of those as disposable. I don't really know if it's designed like that but I treat them as disposable and unreliable so I must have a way to resuscitate the thing when something bad happens.