Skip to content
Snippets Groups Projects
Commit 14053f9d authored by Reiter, Christoph's avatar Reiter, Christoph :snake:
Browse files

docker: Don't run supervisord as root

supervisord complains about being root and this seems to work fine
now if we write the pid file to the user home dir
parent 2c4b7b65
No related branches found
No related tags found
No related merge requests found
Pipeline #85426 passed
...@@ -27,7 +27,7 @@ services: ...@@ -27,7 +27,7 @@ services:
build: build:
context: php-fpm context: php-fpm
working_dir: /application working_dir: /application
entrypoint: sudo supervisord -c /etc/supervisor/conf.d/queue-worker.conf entrypoint: supervisord -c /etc/supervisor/conf.d/queue-worker.conf
volumes: volumes:
- ./php-fpm/queue-worker.conf:/etc/supervisor/conf.d/queue-worker.conf - ./php-fpm/queue-worker.conf:/etc/supervisor/conf.d/queue-worker.conf
- ..:/application - ..:/application
......
...@@ -5,7 +5,7 @@ nodaemon=true ...@@ -5,7 +5,7 @@ nodaemon=true
logfile=/dev/null logfile=/dev/null
logfile_maxbytes=0 logfile_maxbytes=0
# so the log file isn't written to the volume # so the log file isn't written to the volume
pidfile=/supervisord.pid pidfile=/home/user/supervisord.pid
[program:queue-work] [program:queue-work]
command=php /application/bin/console dbp:relay:core:queue:work "%(program_name)s_%(process_num)02d" command=php /application/bin/console dbp:relay:core:queue:work "%(program_name)s_%(process_num)02d"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment