CT Promox Debian 11 Template and openssh-server does not start

[Carsten99]

Hello,

I installed a Promox 7.2-7 environment this days.

I try to use the promox debian 11 template for container.

I installed it and it works but i have a strange SSH Environment.

After reboot/restart of the CT a SSH Server is running as follows:

root@deb2:~# netstat -anlp|grep -i list
tcp6       0      0 :::22                   :::*                    LISTEN      1/init

Strange is the process 1/init.

If I do a restart of the openssh-server by executing

/etc/init.d/ssh restart or
systemctl start ssh

I get the following:

root@deb2:~# netstat -anlp|grep -i list
tcp6       0      0 :::22                   :::*                    LISTEN      324/sshd: /usr/sbin

Now it is the real sshd process.

If I reboot again the other is running again.

It is strange it seams that the daemon ist different, because of the changes I did in /etc/ssh/sshd_config will not be active after reboot.

If I do a /etc/init.d/ssh restart my changes are active.

Why is this the case?

I tested in short with debian 10 template, but it is the same.

My Containerdoes have the following properties:

Protection no
unprivileged container = yes
Feature = nesting = 1


The Boot-Startup looks like:

systemctl list-unit-files --type=service --state=enabled

UNIT FILE                              STATE 
cron.service                           enabled
dbus-org.freedesktop.network1.service  enabled
dbus-org.freedesktop.resolve1.service  enabled
dbus-org.freedesktop.timesync1.service enabled
ifupdown-wait-online.service           enabled
networking.service                     enabled
postfix.service                        enabled
rsyslog.service                        enabled
ssh.service                            enabled
sshd.service                           enabled
syslog.service                         enabled
systemd-boot-check-no-failures.service enabled
systemd-networkd-wait-online.service   enabled
systemd-networkd.service               enabled
systemd-resolved.service               enabled
systemd-time-wait-sync.service         enabled
systemd-timesyncd.service              enabled

Thanks
best regards
Carsten

 

[fabian]

this is normal for socket-activated units..

 

[Carsten99]

Hey Fabian,

thanks alot. Works fine. Found it in your old threat and answer:

systemctl disable ssh.socket

systemctl enable ssh.service

perfectly

thanks
carsten