Lars Boegild Thomsen

The reason is that the above services - in buster - creates a private namespace for temporary files as a security measure. This is not allowed by default for lxc...

Suggested `/etc/apparmor.d/lxc/lxc-default-subutai`: ``` # Do not load this file. Rather, load /etc/apparmor.d/lxc-containers, which # will source all profiles under /etc/apparmor.d/lxc profile lxc-container-default-subutai flags=(attach_disconnected,mediate_deleted) { #include #include deny mount fstype=devpts, mount...

Only an issue with buster++ containers. And it is not even the OS as such but the packaging - buster apache and mariadb are using apparmor features not allowed in...

And how will that influence non-websocket connections?

After import: ``` root@ncpws05:~# subutai list t TEMPLATE -------- debian-buster:subutai:0.5.5 management:jenkins:8.7.4 root@ncpws05:~# subutai list i NAME STATE IP Interface ---- ----- -- --------- management RUNNING 10.10.10.1 eth0 ```

``` root@management:/lib/systemd/system# systemctl status management.service ● management.service - Subutai Management Console Loaded: loaded (/lib/systemd/system/management.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: https://github.com/subutai-io/peer-os/wiki ```

Manual start worked: ``` root@management:/lib/systemd/system# systemctl start management.service root@management:/lib/systemd/system# systemctl status management.service ● management.service - Subutai Management Console Loaded: loaded (/lib/systemd/system/management.service; disabled; vendor preset: enabled) Active: active (running) since Sat...

Sure :) Let me know if you want me to test something when or if you implement it.

Been doing the same pretty much