Bottlerocket for Linux containers, an interesting Amazon Web Services development

AI-generated summary

The discussion centers on Amazon AWS’s Bottlerocket, a Linux-based OS optimized for container hosting, and its potential compatibility with Discourse deployment tools like discourse-setup. D8vid notes that Bottlerocket supports Docker and OCI-formatted images, and references past issues deploying Discourse on Google’s Container-Optimized OS due to restrictive filesystem permissions. He suggests that adapting discourse-setup for such container-focused environments could broaden Discourse’s deployment reach while benefiting from simpler, more secure infrastructure. He proposes enhancements such as prompting admins to supply storage containers and push built images to repos, or even running discourse-setup and launcher inside containers themselves — allowing them to perform host checks and image manipulations while still managing Discourse containers as usual. Falco questions the practical benefit to Discourse, prompting D8vid to elaborate on the trade-offs and architectural possibilities. The conversation highlights a forward-looking exploration of how Discourse might adapt to increasingly container-centric, minimal OS environments like Bottlerocket.

From Phoronix, Amazon AWS Launches Linux-Based Bottlerocket For Hosting Containers, and the Amazon AWS blog, Bottlerocket – Open Source OS for Container Hosting (supports Docker image and images that conform to the Open Container Initiative image format).

It would be interesting to see if discourse-setup works in (or can be adapted to) this environment; when I tried it last year on Google Cloud’s Container-Optimized OS (based on their own stripped-down Linux kernel from ChromeOS), it failed due to the inability to mount any directory with execute permissions (outside of a container, that is).

What benefit Discourse would gain from running on that in your opinion?

If discourse-setup could deploy into container-restricted environments (clearly becoming more popular), the benefit would be a broader base for deployment, but where the targets are actually simpler (and more secure) than a typical ‘fat’ VPS.

Extra steps for the admin would seem a worthy trade-off, e.g. ask if deploying to a different host/container, then exit with basic instructions to supply a storage container & push the built docker image to a repo, so it’s usable on a container-restricted host.

Perhaps discourse-setup itself (and, presumably, also launcher) could run in a container (with the correct run paramaters of course), so that it’s able to make its necessary tests on the target [container] host itself & manipulations of the docker image to be deployed. In that case, funnily enough, launcher would do everything as usual but start/stop Discourse Docker images.