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) 24.Декабрь.2019 21:06:40 7

Нет, не использует, и мы не планируем заставлять его это делать. Рекомендуется обновлять вашу хост-ОС последними патчами безопасности.

Тема		Ответов	Просм.
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	109540	16.01.2025
Install Discourse in Under 30 Minutes Blog	16	15970	03.05.2015
Digital Ocean hosting: Do I need a system admin? Self-hosting hosting	28	6868	14.12.2017
Determining whether my VPS needs any upgrades (generally) Support	20	456	10.03.2025
Completely automatic updates Feature	13	4203	27.06.2018

Использует ли контейнер Discourse unattended-upgrades?

Связанные темы