We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Using chroots in a single Linux Container as an alternative to docker-compose

Formal Metadata

Title
Using chroots in a single Linux Container as an alternative to docker-compose
Title of Series
Number of Parts
779
Author
Contributors
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
StartOS has devised a new strategy for supporting multiple rootfs images for a single application (e.g. nextcloud + postgres). We have elected to do so by creating a single LXC container for the application, that contains each rootfs image, and running each process in a chroot, using bind mounts for special directories such as /proc, /dev, /sys, and /run. This reduces the overhead of multiple containers, but could have drawbacks with respect to compatibility between processes from different distributions, and security within the application. As of the time of this talk, we will have tested an implementation of this strategy, and we will report our findings regarding its advantages and disadvantages.