3 ms·

IMHO: On Docker, I'd say, it will change the rhetorical everything for stateless tiers. Stateful tiers will resist this change. I'm not yet comfortable upgrad

IMHO: On Docker, I'd say, it will change the rhetorical everything for stateless tiers. Stateful tiers will resist this change. I'm not yet comfortable upgrading to a new version of MySQL on a database using Docker in application-container mode, that is, without some package management like scripts (e.g. upgrade the dataset). For stateful tiers, full LXC containers are changing everything, at least until full full-container support arrives in Docker (because, duh, it uses LXC).

shykes 13y ago
> at least until full full-container support arrives in Docker If by "full-container" you mean booting a full /sbin/init in a container, Docker supports that. Just 'docker run /sbin/init' :) > I'm not yet comfortable upgrading to a new version of MySQL on a database using Docker Check out volume sharing `docker run -volumes-from`, it allows you to share the same data volumes between several containers. You can use that primitive to upgrade a database, as well as to run short-lived jobs which affect the dataset: migrations, backups etc.
- josh-wrale 13y ago
  Thank you shykes. I didn't know about the volume sharing. It sounds cool, but I'll need to think more about how such a workflow might work in production. My initial thought is that such a database upgrade would be considerably more difficult to coordinate than say a yum/apt package upgrade. This is unfortunate but it's not entirely a deal breaker (with proper DevOps, anyway). The full container concept is only partially implemented it seems, per the issues linked below. Parity with LXC for a more full VM-like experience would definitely motivate me to adopt Docker quicker in more places (e.g. stateful tiers). Any chance these issues could be given high priority? https://github.com/dotcloud/docker/issues/1960 https://github.com/dotcloud/docker/issues/1960 https://github.com/dotcloud/docker/issues/2276 https://github.com/dotcloud/docker/issues/2276 Thanks, Joshua

shykes 13y ago

> at least until full full-container support arrives in Docker If by "full-container" you mean booting a full /sbin/init in a container, Docker supports that. Just 'docker run /sbin/init' :) > I'm not yet comfortable upgrading to a new version of MySQL on a database using Docker Check out volume sharing `docker run -volumes-from`, it allows you to share the same data volumes between several containers. You can use that primitive to upgrade a database, as well as to run short-lived jobs which affect the dataset: migrations, backups etc.

josh-wrale 13y ago
Thank you shykes. I didn't know about the volume sharing. It sounds cool, but I'll need to think more about how such a workflow might work in production. My initial thought is that such a database upgrade would be considerably more difficult to coordinate than say a yum/apt package upgrade. This is unfortunate but it's not entirely a deal breaker (with proper DevOps, anyway). The full container concept is only partially implemented it seems, per the issues linked below. Parity with LXC for a more full VM-like experience would definitely motivate me to adopt Docker quicker in more places (e.g. stateful tiers). Any chance these issues could be given high priority? https://github.com/dotcloud/docker/issues/1960 https://github.com/dotcloud/docker/issues/1960 https://github.com/dotcloud/docker/issues/2276 https://github.com/dotcloud/docker/issues/2276 Thanks, Joshua