3 ms·

systemd breaks LXC and lmctfy. systemd is not event based (matter of taste, I guess, but I prefer Upstart's model).

herokusaki 13y ago
Looking at to the Arch wiki (https://wiki.archlinux.org/index.php/Lxc-systemd https://wiki.archlinux.org/index.php/Lxc-systemd) it seems like LXC can be at least partially reconciled with systemd. Are there any features of LXC that absolutely can't be made to work with systemd?
deleted 13y ago
[deleted]
SEJeff 13y ago
What are you talking about? CoreOS uses docker + systemd extensively and docker is just a pretty wrapper ontop of lxc. https://coreos.com/docs/launching-containers/launching/getting-started-with-systemd/ https://coreos.com/docs/launching-containers/launching/getti...
- tszming 13y ago
  I don't use coreos/systemd but some people run into issues like this: https://github.com/dotcloud/docker/issues/3629 https://github.com/dotcloud/docker/issues/3629
  - ekidd 13y ago
    Well, that involves running a weird nested stack: The CoreOS systemd, wrapped around a bunch of docker instances, one of which is trying to run the arch Linux systemd inside the container as well. For what it's worth, Docker containers are generally not complete running machines with their own init system. Instead, they're typically a single top-level process running in an isolated container. Basically, they work more like a Heroku app than complete EC2 machine image.
    - FooBarWidget 13y ago
      Exactly. I don't expect Upstart or even SysV init (in the configuration as provided by distributions) to work well inside Docker either. For an example how you should build a Docker container, take a look at http://phusion.github.io/baseimage-docker/ http://phusion.github.io/baseimage-docker/
- CameronNemo 13y ago
  systemd post 204 requires that it is the only cgroups writer, and tramples over every other writer. Some have said that this is because of a decision by upstream kernel maintainers to allow only one cgroups writer, but this decision has not yet happened. Do you know what version of systemd coreOS uses?

Looking at to the Arch wiki (https://wiki.archlinux.org/index.php/Lxc-systemd https://wiki.archlinux.org/index.php/Lxc-systemd) it seems like LXC can be at least partially reconciled with systemd. Are there any features of LXC that absolutely can't be made to work with systemd?

deleted 13y ago

[deleted]

SEJeff 13y ago

What are you talking about? CoreOS uses docker + systemd extensively and docker is just a pretty wrapper ontop of lxc. https://coreos.com/docs/launching-containers/launching/getting-started-with-systemd/ https://coreos.com/docs/launching-containers/launching/getti...

tszming 13y ago
I don't use coreos/systemd but some people run into issues like this: https://github.com/dotcloud/docker/issues/3629 https://github.com/dotcloud/docker/issues/3629
- ekidd 13y ago
  Well, that involves running a weird nested stack: The CoreOS systemd, wrapped around a bunch of docker instances, one of which is trying to run the arch Linux systemd inside the container as well. For what it's worth, Docker containers are generally not complete running machines with their own init system. Instead, they're typically a single top-level process running in an isolated container. Basically, they work more like a Heroku app than complete EC2 machine image.
  - FooBarWidget 13y ago
    Exactly. I don't expect Upstart or even SysV init (in the configuration as provided by distributions) to work well inside Docker either. For an example how you should build a Docker container, take a look at http://phusion.github.io/baseimage-docker/ http://phusion.github.io/baseimage-docker/
CameronNemo 13y ago
systemd post 204 requires that it is the only cgroups writer, and tramples over every other writer. Some have said that this is because of a decision by upstream kernel maintainers to allow only one cgroups writer, but this decision has not yet happened. Do you know what version of systemd coreOS uses?