Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade supervisord to 3.3.3 and fix supervisord.conf #1390

Merged
merged 22 commits into from
Feb 14, 2018
Merged
Show file tree
Hide file tree
Changes from 20 commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions dockers/docker-base/etc/supervisor/supervisord.conf
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,14 @@
[unix_http_server]
file=/var/run/supervisor.sock ; (the path to the socket file)
chmod=0700 ; sockef file mode (default 0700)
username=nobody
password=nobody

[supervisord]
logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
childlogdir=/var/log/supervisor ; ('AUTO' child log dir, default $TEMP)
user=root

; the below section must remain in the config file for RPC
; (supervisorctl/web interface) to work, additional interfaces may be
Expand All @@ -17,6 +20,8 @@ supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL for a unix socket
username=nobody
password=nobody
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this mean we need to type username and password for supervisorctl command line? is that necessary?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from your commit message, you are trying to address http server accessing issue, so I am not sure if we need to add username/password for the supervisorctl command line as well. Since once you can get into the docker, you already have sudo privilege, adding extra user/pass protection does not seem necessary.


; The [include] section can just contain the "files" setting. This
; setting can list multiple files (separated by whitespace or
Expand Down
2 changes: 1 addition & 1 deletion rules/supervisor.mk
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# supervisor package

SUPERVISOR_VERSION = 3.3.2
SUPERVISOR_VERSION = 3.3.3

export SUPERVISOR_VERSION

Expand Down