# Bottlerocket for Linux containers, an interesting Amazon Web Services development
**URL:** https://meta.discourse.org/t/bottlerocket-for-linux-containers-an-interesting-amazon-web-services-development/143897
**Category:** Development
**Created:** [March 11, 2020, 11:21am UTC](https://meta.discourse.org/t/bottlerocket-for-linux-containers-an-interesting-amazon-web-services-development/143897 "2020-03-11T11:21:04Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@D8vid](https://meta.discourse.org/u/D8vid)
#### Post date: [March 11, 2020, 11:21am UTC](https://meta.discourse.org/t/bottlerocket-for-linux-containers-an-interesting-amazon-web-services-development/143897/1 "2020-03-11T11:21:04Z")
From Phoronix, [Amazon AWS Launches Linux-Based Bottlerocket For Hosting Containers](https://www.phoronix.com/scan.php?page=news_item&px=Amazon-AWS-Bottlerocket), and the Amazon AWS blog, [Bottlerocket – Open Source OS for Container Hosting](https://aws.amazon.com/blogs/aws/bottlerocket-open-source-os-for-container-hosting/) (supports Docker image and images that conform to the [Open Container Initiative](https://www.opencontainers.org/) 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](https://cloud.google.com/container-optimized-os/docs) (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).
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 11, 2020, 2:29pm UTC](https://meta.discourse.org/t/bottlerocket-for-linux-containers-an-interesting-amazon-web-services-development/143897/2 "2020-03-11T14:29:02Z")
What benefit Discourse would gain from running on that in your opinion?
---
### Author:  [@D8vid](https://meta.discourse.org/u/D8vid)
#### Post date: [March 11, 2020, 9:26pm UTC](https://meta.discourse.org/t/bottlerocket-for-linux-containers-an-interesting-amazon-web-services-development/143897/3 "2020-03-11T21:26:54Z")
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.