Amazon-ssm-agent 無法識別的服務（剛剛通過 Docker 安裝）

Question

我試圖弄清楚為什么我無法在 Ubuntu 20.04.1 LTS 主機上運行的 Kali Linux Focker 映像中手動啟動和停止amazon-ssm-agent服務。 根據他們的指示，我獲得了.deb文件並使用dpkg -i安裝了它。 雖然我可以通過amazon-ssm-agent -h與它進行交互並很好地注冊它等等，但我無法重新啟動服務，這有時會在注冊后修復連接丟失問題。

正如您在下面看到的，我正在使用wget獲取.deb文件並安裝它：

➜  ~   wget https://s3.us-east-1.amazonaws.com/amazon-ssm-us-east-1/latest/debian_amd64/amazon-ssm-agent.deb
--2020-12-27 22:21:32--  https://s3.us-east-1.amazonaws.com/amazon-ssm-us-east-1/latest/debian_amd64/amazon-ssm-agent.deb
Resolving s3.us-east-1.amazonaws.com (s3.us-east-1.amazonaws.com)... 52.217.109.126
Connecting to s3.us-east-1.amazonaws.com (s3.us-east-1.amazonaws.com)|52.217.109.126|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41537900 (40M) [binary/octet-stream]
Saving to: 'amazon-ssm-agent.deb'

amazon-ssm-agent.deb                                                                       100%[========================================================================================================================================================================================================================================>]  39.61M   105MB/s    in 0.4s

2020-12-27 22:21:33 (105 MB/s) - 'amazon-ssm-agent.deb' saved [41537900/41537900]

➜  ~ dpkg -i amazon-ssm-agent.deb
Selecting previously unselected package amazon-ssm-agent.
(Reading database ... 231292 files and directories currently installed.)
Preparing to unpack amazon-ssm-agent.deb ...
Preparing for install
Unpacking amazon-ssm-agent (3.0.431.0-1) ...
Setting up amazon-ssm-agent (3.0.431.0-1) ...
Starting agent
➜  ~ service amazon-ssm-agent status
amazon-ssm-agent: unrecognized service
➜  ~

由於以下錯誤，我也無法使用systemctl ：

➜  ~ systemctl status amazon-ssm-agent
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
➜  ~

我也嘗試查看/etc/init.d ，但沒有運氣：

➜  ~ ls /etc/init.d -l
total 240
-rwxr-xr-x 1 root root 2489 Aug  8 07:47 apache-htcacheclean
-rwxr-xr-x 1 root root 8181 Aug  8 07:47 apache2
-rwxr-xr-x 1 root root 1614 Jul 14  2019 atftpd
-rwxr-xr-x 1 root root 2401 May 26  2020 avahi-daemon
-rwxr-xr-x 1 root root 1175 Apr 17  2020 binfmt-support
-rwxr-xr-x 1 root root 2948 Sep 16 07:49 bluetooth
-rwxr-xr-x 1 root root 1232 Dec  1 01:02 console-setup.sh
-rwxr-xr-x 1 root root  937 Sep  3 22:30 cryptdisks
-rwxr-xr-x 1 root root  896 Sep  3 22:30 cryptdisks-early
-rwxr-xr-x 1 root root 3152 Jul  2 13:19 dbus
-rwxr-xr-x 1 root root 1408 Aug  4 23:00 dns2tcp
-rwxr-xr-x 1 root root 7159 May 23  2020 exim4
-rwxr-xr-x 1 root root 3708 Nov 25 21:07 hwclock.sh
-rwxr-xr-x 1 root root 3615 Sep  5  2019 inetsim
-rwxr-xr-x 1 root root 4113 Sep 26 16:48 iodined
-rwxr-xr-x 1 root root 1479 Oct  9  2016 keyboard-setup.sh
-rwxr-xr-x 1 root root 2044 Apr 18  2020 kmod
-rwxr-xr-x 1 root root 5966 Nov 22 15:42 mariadb
-rwxr-xr-x 1 root root 2882 Jul 26  2019 miredo
-rwxr-xr-x 1 root root 4486 Sep 21 14:45 networking
-rwxr-xr-x 1 root root 5658 Jul 26 12:02 nfs-common
-rwxr-xr-x 1 root root 4579 May 28  2020 nginx
-rwxr-xr-x 1 root root 1934 Jul  7 05:55 nmbd
-rwxr-xr-x 1 root root 1494 Sep 23 11:46 ntp
-rwxr-xr-x 1 root root 9138 Oct 28 18:37 openvpn
-rwxr-xr-x 1 root root 3720 Jun 14  2020 pcscd
-rwxr-xr-x 1 root root 1490 Nov 15  2019 postgresql
-rwxr-xr-x 1 root root  924 May 16  2020 procps
-rwxr-xr-x 1 root root 3699 Jul 22  2017 ptunnel
-rwxr-xr-x 1 root root 3836 Jan  2  2017 redsocks
-rwxr-xr-x 1 root root 1615 Aug 19  2018 rlinetd
-rwxr-xr-x 1 root root 2507 Jul 13 01:22 rpcbind
-rwxr-xr-x 1 root root 4417 Aug 26 20:23 rsync
-rwxr-xr-x 1 root root 2864 Oct 20 19:45 rsyslog
-rwxr-xr-x 1 root root 1661 Jun  5  2013 rwhod
-rwxr-xr-x 1 root root 2259 Jul  7 05:55 samba-ad-dc
-rwxr-xr-x 1 root root 1222 Apr  2  2017 screen-cleanup
-rwxr-xr-x 1 root root 3088 Oct 10  2019 smartmontools
-rwxr-xr-x 1 root root 2061 Jul  7 05:55 smbd
-rwxr-xr-x 1 root root 1175 Sep 24 23:10 snmpd
-rwxr-xr-x 1 root root 4056 Dec  2 10:32 ssh
-rwxr-xr-x 1 root root 4440 Sep  5  2019 sslh
-rwxr-xr-x 1 root root 5730 Sep 13 10:43 stunnel4
-rwxr-xr-x 1 root root 1030 Dec  2 03:10 sudo
-rwxr-xr-x 1 root root 1581 Dec 16 08:36 sysstat
-rwxr-xr-x 1 root root 6871 Dec  3 22:53 udev
-rwxr-xr-x 1 root root 2757 Oct  9 08:13 x11-common
➜  ~

但是，您可以看到運行amazon-ssm-agent命令運行良好：

➜  ~ amazon-ssm-agent
Error occurred fetching the seelog config file path:  open /etc/amazon/ssm/seelog.xml: no such file or directory
Initializing new seelog logger
New Seelog Logger Creation Complete
2020-12-27 22:24:08 ERROR error fetching the instanceID, Failed to fetch instance ID. Data from vault is empty. EC2MetadataError: failed to make EC2Metadata request
        status code: 404, request id:
caused by: not found
2020-12-27 22:24:08 ERROR error occurred when starting amazon-ssm-agent: error fetching the instanceID, Failed to fetch instance ID. Data from vault is empty. EC2MetadataError: failed to make EC2Metadata request
        status code: 404, request id:
caused by: not found
➜  ~

注冊后我需要重新啟動服務的唯一原因是，有時我在注冊后托管實例的 ping 狀態會出現“連接丟失”。 通常重新啟動服務似乎對我有用。

我能夠在僅使用主機（Ubuntu 20.04）時成功重啟服務，即使主機也在運行 Kali Linux，但當它是 docker 容器時，這對我沒有任何意義，因為一切都是功能除了能夠手動啟動/停止服務。

Answer 1

我可以通過克隆這個存儲庫來運行它： https://github.com/gdraheim/docker-systemctl-replacement

克隆后，我運行以下命令：

/root/docker-systemctl-replacement/files/docker/systemctl.py restart amazon-ssm-agent