Hi, After upgrading our discourse instance, I noticed that the process sidekiq is running as a regular machine user. Being in a VM hosted on GCP, the process picks a random user. I’m not sure if this is a bug or expected. On my side is a little bit of weird behavior and potential security issues. …

Mine appears to be running as user “ubuntu” which I believe is the default user? But then so are my unicorns.

UIDs in the container doesn’t map to the same UIDs in the host. You can’t simply read the top output from the host.

Sidekiq se ejecuta como usuario

Falco (Falco) 4 Febrero, 2025 14:53 3

Las UIDs en el contenedor no se corresponden con las mismas UIDs en el host. No se puede simplemente leer la salida de top del host.

Tema		Respuestas	Vistas
Which system user account(s) should Discourse spawned processes run as? Self-hosting	6	450	24 Febrero 2023
Unicorn.conf.rb attach account Self-hosting	8	1096	24 Abril 2019
Other (all?) system's user involved somehow? Self-hosting	4	348	21 Septiembre 2023
Docker processes running as non-root? Any way to specify user? Support docker	9	4414	12 Noviembre 2018
"Ensure sidekiq is running." when it is definitely running Self-hosting	19	7858	24 Octubre 2015