Bottlerocket OS Docker Compose Variant

[rajivr]

I've been working on a Bottlerocket OS Docker Compose variant.

You can find the GitHub repository here. I've shared my reasoning for creating the variant in the README.md.

Besides packaging Docker Compose, the variant provides settings API to manage Docker Compose applications.

I would really appreciate if you could please take a look and let me know your feedback.

Also if you feel this might be interesting to other AWS customers, and if you could provide an official AMI, I'll be very happy to see this work merged upstream.

[bcressey]

Very nice, @rajivr! I love it.

For the individual compose applications, did you consider a settings API to allow bundling the contents inline? Something like:

[settings.compose-containers.app]
enabled = true
payload = "<base64 of zip or tar gz>"

If the payload seems likely to get very large (> 16 KiB) then the long-awaited change in bottlerocket-os/bottlerocket-core-kit#554 would help - it will let apiclient apply pull in a settings TOML from S3 or SSM, and can be used in a bootstrap command to avoid the container dependency.

Also if you feel this might be interesting to other AWS customers, and if you could provide an official AMI, I'll be very happy to see this work merged upstream.

This certainly could be interesting to other AWS customers, though official AMIs aren't very likely without a lot of demand.

We could move it to bottlerocket-community, if you're interested in maintaining it there.

[rajivr]

For the individual compose applications, did you consider a settings API to allow bundling the contents inline? Something like:

[settings.compose-containers.app]
enabled = true
payload = "<base64 of zip or tar gz>"

Yes, the technical reason was the 16KiB limitation with user-data. However from an automation point of view, I preferred having a simple user_data.toml that I could visually inspect and understand. This feature can be easily added, if other users need it, with something like

[settings.compose-containers.app]
enabled = true
use_payload = true # defaults to `false`
payload = "<base64 of zip or tar gz>"

[...]

This certainly could be interesting to other AWS customers, though official AMIs aren't very likely without a lot of demand.

We could move it to bottlerocket-community, if you're interested in maintaining it there.

Sure, I'll be very happy to move it to Bottlerocket Community. I'll initiate the transfer on Monday, so we don't run into the one-day limit due to the weekend.

[rajivr]

It looks like I need write access to the bottlerocket-community organization to make the direct transfer to the organization. I have initiated the transfer request to @bcressey. Please approve and move to bottlerocket-community org. 🙏

[bcressey]

It looks like I need write access to the bottlerocket-community organization to make the direct transfer to the organization. I have initiated the transfer request to @bcressey. Please approve and move to bottlerocket-community org. 🙏

If you don't mind, I'd like to create the repo first so it starts with the correct policy documents e.g. SECURITY.md and CODE_OF_CONDUCT.md. Then I can add you as an admin and one of us can merge in the existing commits from your project using steps like this.

It's not a hard requirement but would help avoid surprising any internal teams that might be tracking such things.

[rajivr]

If you don't mind, I'd like to create the repo first so it starts with the correct policy documents e.g. SECURITY.md and CODE_OF_CONDUCT.md. Then I can add you as an admin and one of us can merge in the existing commits from your project using steps like this.

Sure, that works! Please go ahead and create a repository with the required files. If you would like to integrate the commits, from rajivr/bottlerocket-compose, that is also fine. I'll then create a pointer to the new repository in the README.md and archive the current repository.

[bcressey]

I've been on vacation for a bit, but I'll pick this up again this week.