systemd внутри LXC

0

2

Имеется Debian 8.5 Jessie в роли хоста и настроенный LXC 2.0 для запуска непривилегированых контейнеров, где создан контейнер с таким же Debian Jessie. Проблема в том, что контейнер стартует очень долго и проходит около пары минут, прежде чем я могу в него зайти по ssh, так же его невозможно погасить изнутри и он долго выключается через lxc-stop. Как я понимаю проблема с systemd или правильной настройкой для его работы с непривилегироваными контейнерами.

После логина получаю такое:

builduser@builder:~$ sudo systemctl status
● builder
    State: starting
     Jobs: 11 queued
   Failed: 2 units
    Since: Wed 2016-06-15 09:36:26 UTC; 2min 18s ago
   CGroup: /user.slice/user-1000.slice/session-1.scope/lxc/builder
           └─1 /sbin/init

builduser@builder:~$ sudo systemctl --failed
  UNIT                LOAD   ACTIVE SUB    JOB   DESCRIPTION
● dev-hugepages.mount loaded failed failed       Huge Pages File System
● dbus.service        loaded failed failed start D-Bus System Message Bus

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
JOB    = Pending job for the unit.

2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

builduser@builder:~$ sudo systemctl status dev-hugepages.mount
● dev-hugepages.mount - Huge Pages File System
   Loaded: loaded (/lib/systemd/system/dev-hugepages.mount; static)
   Active: failed (Result: exit-code) since Wed 2016-06-15 09:36:54 UTC; 4min 45s ago
    Where: /dev/hugepages
     What: hugetlbfs
     Docs: https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt
           http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
  Process: 89 ExecMount=/bin/mount -n hugetlbfs /dev/hugepages -t hugetlbfs (code=exited, status=32)

Jun 15 09:36:52 builder mount[89]: mount: permission denied
Jun 15 09:36:54 builder systemd[1]: dev-hugepages.mount mount process exited, code=exited status=32
Jun 15 09:36:54 builder systemd[1]: Failed to mount Huge Pages File System.
Jun 15 09:36:54 builder systemd[1]: Unit dev-hugepages.mount entered failed state.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

builduser@builder:~$ sudo systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static)
   Active: failed (Result: exit-code) since Wed 2016-06-15 09:37:46 UTC; 4min 40s ago
     Docs: man:dbus-daemon(1)
  Process: 171 ExecStart=/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation (code=exited, status=206/OOM_ADJUST)
 Main PID: 171 (code=exited, status=206/OOM_ADJUST)

Jun 15 09:36:55 builder systemd[1]: Started D-Bus System Message Bus.
Jun 15 09:37:46 builder systemd[1]: dbus.service: main process exited, code=exited, status=206/OOM_ADJUST
Jun 15 09:37:46 builder systemd[1]: Failed to kill control group: Invalid argument
Jun 15 09:37:46 builder systemd[1]: Failed to kill control group: Invalid argument
Jun 15 09:37:46 builder systemd[1]: Failed to kill control group: Invalid argument
Jun 15 09:37:46 builder systemd[1]: Failed to kill control group: Invalid argument
Jun 15 09:37:46 builder systemd[1]: Unit dbus.service entered failed state.

Лог journalctl -b http://pastebin.com/FbA5nNfP

При попытке выключить:

builduser@builder:~$ sudo poweroff
Warning! D-Bus connection terminated.
Failed to wait for response: Success
Failed to open initctl FIFO: No such device or address
Failed to talk to init daemon.

Лог загрузки http://pastebin.com/4Z3wZZXV

Подскажите, как это дело всё подружить?

Ссылка

Похожие темы