docker run -d --name zkui -p 19090:9090 -e ZKUI_ZK_SERVER=host.docker.internal:2181 qnib/zkui:latest
Logs
2022-05-23 09:19:10,932 CRIT Supervisor running as root (no user in config file)
2022-05-23 09:19:10,932 INFO Included extra file "/etc/supervisord.d/consul.ini" during parsing
2022-05-23 09:19:10,932 INFO Included extra file "/etc/supervisord.d/rsyslog.ini" during parsing
2022-05-23 09:19:10,932 INFO Included extra file "/etc/supervisord.d/rsyslog_conf.ini" during parsing
2022-05-23 09:19:10,933 INFO Included extra file "/etc/supervisord.d/zkui-update.ini" during parsing
2022-05-23 09:19:10,933 INFO Included extra file "/etc/supervisord.d/zkui.ini" during parsing
2022-05-23 09:19:10,948 INFO RPC interface 'supervisor' initialized
2022-05-23 09:19:10,948 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-05-23 09:19:10,948 INFO supervisord started with pid 1
2022-05-23 09:19:11,954 INFO spawned: 'zkui-update' with pid 66
2022-05-23 09:19:11,956 INFO spawned: 'consul' with pid 67
2022-05-23 09:19:11,959 INFO spawned: 'rsyslog-conf' with pid 68
2022-05-23 09:19:11,961 INFO spawned: 'rsyslog' with pid 70
2022-05-23 09:19:12,117 INFO spawned: 'zkui' with pid 293
2022-05-23 09:19:13,120 INFO success: zkui-update entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-23 09:19:13,121 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-23 09:19:13,121 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-23 09:19:13,666 INFO exited: zkui (exit status 1; not expected)
2022-05-23 09:19:14,670 INFO spawned: 'zkui' with pid 323
2022-05-23 09:19:15,672 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-23 09:19:16,097 INFO exited: zkui (exit status 1; not expected)
2022-05-23 09:19:16,115 INFO spawned: 'zkui' with pid 363
2022-05-23 09:19:16,978 INFO success: consul entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2022-05-23 09:19:17,322 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-23 09:19:17,554 INFO exited: zkui (exit status 1; not expected)
2022-05-23 09:19:18,139 INFO spawned: 'zkui' with pid 392
2022-05-23 09:19:18,140 INFO exited: zkui-update (exit status 0; expected)
2022-05-23 09:19:19,141 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-23 09:19:19,509 INFO exited: zkui (exit status 1; not expected)
2022-05-23 09:19:20,512 INFO spawned: 'zkui' with pid 421
2022-05-23 09:19:21,517 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-23 09:19:22,012 INFO exited: zkui (exit status 1; not expected)
Steps to reproduce
docker run -d --name zkui -p 19090:9090 -e ZKUI_ZK_SERVER=host.docker.internal:2181 qnib/zkui:latest
Logs
2022-05-23 09:19:10,932 CRIT Supervisor running as root (no user in config file) 2022-05-23 09:19:10,932 INFO Included extra file "/etc/supervisord.d/consul.ini" during parsing 2022-05-23 09:19:10,932 INFO Included extra file "/etc/supervisord.d/rsyslog.ini" during parsing 2022-05-23 09:19:10,932 INFO Included extra file "/etc/supervisord.d/rsyslog_conf.ini" during parsing 2022-05-23 09:19:10,933 INFO Included extra file "/etc/supervisord.d/zkui-update.ini" during parsing 2022-05-23 09:19:10,933 INFO Included extra file "/etc/supervisord.d/zkui.ini" during parsing 2022-05-23 09:19:10,948 INFO RPC interface 'supervisor' initialized 2022-05-23 09:19:10,948 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2022-05-23 09:19:10,948 INFO supervisord started with pid 1 2022-05-23 09:19:11,954 INFO spawned: 'zkui-update' with pid 66 2022-05-23 09:19:11,956 INFO spawned: 'consul' with pid 67 2022-05-23 09:19:11,959 INFO spawned: 'rsyslog-conf' with pid 68 2022-05-23 09:19:11,961 INFO spawned: 'rsyslog' with pid 70 2022-05-23 09:19:12,117 INFO spawned: 'zkui' with pid 293 2022-05-23 09:19:13,120 INFO success: zkui-update entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-23 09:19:13,121 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-23 09:19:13,121 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-23 09:19:13,666 INFO exited: zkui (exit status 1; not expected) 2022-05-23 09:19:14,670 INFO spawned: 'zkui' with pid 323 2022-05-23 09:19:15,672 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-23 09:19:16,097 INFO exited: zkui (exit status 1; not expected) 2022-05-23 09:19:16,115 INFO spawned: 'zkui' with pid 363 2022-05-23 09:19:16,978 INFO success: consul entered RUNNING state, process has stayed up for > than 5 seconds (startsecs) 2022-05-23 09:19:17,322 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-23 09:19:17,554 INFO exited: zkui (exit status 1; not expected) 2022-05-23 09:19:18,139 INFO spawned: 'zkui' with pid 392 2022-05-23 09:19:18,140 INFO exited: zkui-update (exit status 0; expected) 2022-05-23 09:19:19,141 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-23 09:19:19,509 INFO exited: zkui (exit status 1; not expected) 2022-05-23 09:19:20,512 INFO spawned: 'zkui' with pid 421 2022-05-23 09:19:21,517 INFO success: zkui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-23 09:19:22,012 INFO exited: zkui (exit status 1; not expected)