Our great sponsors
-
-
sysbox
An open-source, next-generation "runc" that empowers rootless containers to run workloads such as Systemd, Docker, Kubernetes, just like VMs.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Done it with https://github.com/daplanet/datagrid
This is what I would do instead. Install Sysbox in your host (assuming Linux) and launch a system-container inside of which all your app containers will live, including a dedicated docker engine and portainer itself. By doing this you are isolating your host, while at the same time, you are achieving your goal of encapsulating your entire stack in a single docker image, which you can now take with you anywhere and re-instantiate by doing a simple docker run.
Related posts
- Individual Docker Desktops vs hosting on a server?
- Sysbox now works on K8s v1.21
- Does running a container with privileged mode turn on allow code to escape into the Host ?
- How to containerize an app that is not native to Docker ecosystem?
- Weird question: Is it possible to run docker inside of a docker instance?