In a discussion on High Availability setups for Discourse, Rob_Spencer asks if two web containers (web1 and web2) can share the same volumes. pfaffman suggests Amazon S3 as an alternative and questions the need for multiple web containers on one host. sam confirms that shared web volumes can be shared, but logs must remain separate, joking that running two web containers on one host is “NINJA level.” Rob_Spencer explains the goal is to avoid downtime during rebuilds, noting that running containers across separate servers is redundant on a high-availability cloud platform. pfaffman suggests bootstrapping a new web container without stopping the old one, swapping them after completion for minimal downtime. Rob_Spencer asks about rollback options, and pfaffman replies to simply leave the old container running. Rob_Spencer clarifies confusion, proposing naming the new container differently for easier rollback. qianqiang adds that remote disk mounting could be considered even across different machines. The thread highlights practical container management strategies for minimizing downtime while cautioning against over-engineering HA setups.
This is a good question. It seems like one way to solve this problem is to use Amazon S3. A related question is, if you have multiple web containers across multiple servers, then what do you do?
You can point shared web to be the same but logs need to be separate.
Though I have no idea why you would run 2 web containers on same host, this is NINJA level setup. If you are in NINJA mode I am surprised you even have these questions
NInja master say “never assume you know everything, always ask person who wrote the damn thing”
Thanks, I’ll try this out.
The two web containers gets around the downtime while rebuilding a container. There’s no value in running them on two separate servers, which it’s already running on a high availability cloud platform. There’s a weird temptation to build HA on top of HA, but it’s just a waste of resources and ends up with server sprawl
If you have a separate data and web containers you can bootstrap the web container without stopping the one that’s running. When it’s done you then destroy the old one and start the new one. Down time is only a few seconds.
How do you start the same one? I would be easier to create a new one with a different name, an have the old one in standby in case you need to roll back.