Does the Discourse docker container use unattended-upgrades to keep its Debian-backed docker container’s OS packages up-to-date? I noticed that the INSTALL-cloud.md guide recommends installing unattended-upgrades on the docker host machine, so I got wondering about the state of the OS packages insi…

After further digging, it appears that unattended-upgrades is installed but not running on the Discourse docker container. First, it’s clearly installed root@osestaging1-discourse-ose:/var/www/discourse# dpkg -l | grep -i unatt ii unattended-upgrades 1.11.2 all …

My guess is that it’s off on purpose as it might break something, and the image itself is updated when a serious security issue is found. You can enable it if you want, just enter the container.

Actually, I just realized that Discourse’s docker image is setup to use runit. Is systemd even installed on the Discourse docker container? My guess is not having systemd installed is what’s breaking unattended-upgrades.

Sounds right. Some people really don’t like systemd. So you can either trust that the base container gets updated regularly by people running a large team of professionals that depends on it, or you can do it some other way yourself and hope that you don’t break anything.

[이미지] maltfield: But what about the Discourse docker container? Does it use unattended-upgrades ? No it doesn’t and we don’t plan to make it use. The recommendation is to keep your host OS updated with the latest security patches.

[이미지] pfaffman: So you can either trust that the base container gets updated regularly by people running a large team of professionals that depends on it, Which, for the record, it is.

fyi, I fixed the broken unattended-upgrades install (which doesn’t actually run without systemd on the Discourse docker container) by triggering it to run via a cron job. I created the following yaml template file in my /var/discourse/templates/ dir to create the necessary cron job (note that it al…

It seems that it is enabled on a fresh Discourse docker image (running Debian 10). It is launched through runit → cron → /etc/cron.daily/apt-compat → /usr/lib/apt/apt.systemd.daily It was also running on a one-year-old Ubuntu 16-based docker image (based on discourse/base:2.0.20190321-0122), I am p…

[이미지] tormod: It is launched through runit → cron → /etc/cron.daily/apt-compat → /usr/lib/apt/apt.systemd.daily systemd isn’t installed, so it never actually runs.

Discourse 컨테이너가 unattended-upgrades를 사용합니까?

지원 자체 호스팅

Falco (Falco) 12월 24, 2019, 9:06오후 7

아니요, 사용하지 않으며 그렇게 할 계획도 없습니다. 호스트 OS를 최신 보안 패치가 적용된 상태로 유지하는 것이 권장됩니다.

글		댓글	조회수
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	111355	1월 16, 2025
Install Discourse in Under 30 Minutes Blog	16	16474	5월 3, 2015
Digital Ocean hosting: Do I need a system admin? Self-hosting hosting	28	7108	12월 14, 2017
Determining whether my VPS needs any upgrades (generally) Support	20	898	3월 10, 2025
Completely automatic updates Feature	13	4351	6월 27, 2018

Discourse 컨테이너가 unattended-upgrades를 사용합니까?

Related topics