87ea2a4794
The current supervisord condifguration sets up the HTTP server to listen on a tcp socket which is private i.e. available only on localhost. This poses a regression where multiple containers cannot be run if the host network interface is used when docker container is run with `--network host` option. This change adds a new env variable `SUPERVISOR_SERVER`, with potential values `unix | private_port | public_port`, where `unix` is set as the default value. By default, the HTTP server is now set to listen on a UNIX domain socket. The file path is set to `/etc/supervisor/supervisor.sock` instead of the /tmp directory since some systems periodically delete older files in /tmp. If the socket file is deleted, supervisorctl will be unable to connect to supervisord. When SUPERVISOR_SERVER is set to `public_port` or `private_port`, the HTTP server is set to listen on a TCP socket. Resolves https://github.com/storj/storj/issues/4661 Change-Id: I224836dcae0293bcfe49874f2748be7723944687 |
||
|---|---|---|
| .. | ||
| docker | ||
| docker-base | ||
| dashboard.go | ||
| deprecated.go | ||
| Dockerfile | ||
| Dockerfile.base | ||
| gracefulexit_test.go | ||
| gracefulexit.go | ||
| main_test.go | ||
| main.go | ||
| service_nonwindows.go | ||
| service_windows.go | ||
| storagenode.yaml | ||