dvasdekis/ib-gateway-docker-gcp

/usr/bin/xvfb-run: 184: 0: not found

tbrown122387 opened this issue · 2 comments

tbrown122387 commented

I'm running a modified version of this, and whenever I try to docker-compose up --build everything, I keep getting the error /usr/bin/xvfb-run: 184: 0: not found. Here's a snippet of the output:

ib_logger_app | 2020-12-30 18:29:51,539 INFO spawned: 'ibdies' with pid 8
ib_logger_app | 2020-12-30 18:29:51,543 INFO spawned: 'ibcontroller' with pid 9
ib_logger_app | 2020-12-30 18:29:51,545 INFO spawned: 'socat_live' with pid 10
ib_logger_app | 2020-12-30 18:29:51,548 INFO spawned: 'socat_paper' with pid 11
ib_logger_app | /usr/bin/xvfb-run: 184: 0: not found
ib_logger_app | 2020-12-30 18:29:51,662 INFO exited: ibcontroller (exit status 127; not expected)
ib_logger_app | 2020-12-30 18:29:52,678 INFO success: ibdies entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ib_logger_app | 2020-12-30 18:29:52,680 INFO spawned: 'ibcontroller' with pid 52
ib_logger_app | 2020-12-30 18:29:52,680 INFO success: socat_live entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ib_logger_app | 2020-12-30 18:29:52,680 INFO success: socat_paper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ib_logger_app | /usr/bin/xvfb-run: 184: 0: not found
ib_logger_app | 2020-12-30 18:29:52,753 INFO exited: ibcontroller (exit status 127; not expected)
ib_logger_app | 2020-12-30 18:29:54,758 INFO spawned: 'ibcontroller' with pid 93
ib_logger_app | /usr/bin/xvfb-run: 184: 0: not found
ib_logger_app | 2020-12-30 18:29:54,837 INFO exited: ibcontroller (exit status 127; not expected)
ib_logger_app | 2020-12-30 18:29:57,842 INFO spawned: 'ibcontroller' with pid 134
ib_logger_app | /usr/bin/xvfb-run: 184: 0: not found
ib_logger_app | 2020-12-30 18:29:57,920 INFO exited: ibcontroller (exit status 127; not expected)
ib_logger_app | 2020-12-30 18:29:58,921 INFO gave up: ibcontroller entered FATAL state, too many start retries too quickly
ib_logger_app | 2020-12-30 18:29:59,932 WARN ibdies: has entered the UNKNOWN state and will no longer receive events, this usually indicates the process violated the eventlistener protocol
ib_logger_app | 2020-12-30 18:29:59,932 WARN received SIGTERM indicating exit request
ib_logger_app | 2020-12-30 18:29:59,932 INFO waiting for ibdies, socat_live, socat_paper to die
ib_logger_app | 2020-12-30 18:29:59,933 INFO stopped: socat_paper (exit status 143)
ib_logger_app | 2020-12-30 18:29:59,934 INFO stopped: socat_live (exit status 143)
ib_logger_app | 2020-12-30 18:30:00,936 INFO stopped: ibdies (terminated by SIGTERM)
ib_logger_app | 2020-12-30 18:30:02,199 INFO Set uid to user 0 succeeded
ib_logger_app | 2020-12-30 18:30:02,202 INFO supervisord started with pid 6
ib_logger_app | 2020-12-30 18:30:03,204 INFO spawned: 'ibdies' with pid 8
ib_logger_app | 2020-12-30 18:30:03,208 INFO spawned: 'ibcontroller' with pid 9
ib_logger_app | 2020-12-30 18:30:03,210 INFO spawned: 'socat_live' with pid 10
ib_logger_app | 2020-12-30 18:30:03,213 INFO spawned: 'socat_paper' with pid 11
ib_logger_app | /usr/bin/xvfb-run: 184: 0: not found

Why is this happening? "0" not found? Isn't that set in docker-compose.yml

XVFB_ARGS: "-ac -screen 0 1024x768x16 +extension RANDR"
tbrown122387 commented

I was mixing and matching the different ways to input environment variables in docker-compose.yml. now fixed

tbrown122387 commented