-
Notifications
You must be signed in to change notification settings - Fork 161
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
Cannot run docker-compose - python not found #16
Comments
I think this is a docker-compose issue. You are probably running this on Ubuntu 18.04 LTS or similar since afaik they do not sym link The best course of action to take is to manually create a symbolic link python -> python3: sudo ln -s /usr/bin/python3 /usr/bin/python |
python is installed. as far as i can see this error is from within the docker instance. didnt the python upstream change the default command from python to python3 in a recent version?
|
The container image should be okay, since you are the first to report this issue. Can you confirm you can run the following: docker run --rm python:3.7-stretch python --version This is the what the container uses: https://github.com/greenstatic/bigbluebutton-exporter/blob/master/Dockerfile#L1 If it works, then the container should work as well. Try creating the bbb-exporter container manually instead of using docker compose; docker run --rm greenstatic/bigbluebutton-exporter:v0.2.0 You should get a KeyError: 'API_BASE_URL' since we didn't supply any environment variables not a:
If you get a KeyError then the container works and you have a docker-compose issue. |
the python command works, but sadly the docker run bbbexporter does not, same error:
all other docker-compose and docker run commands work (including greenlight) |
This is very strange. docker run --rm --entrypoint python3 greenstatic/bigbluebutton-exporter:v0.2.0 |
same error :-/ |
Can you also run docker image ls And paste both lines for python and greenstatic/bigbluebutton-exporter. |
|
We are running the exact same python and bbb-exporter docker images. This must be a docker host issue. Can you specify the following:
|
Ubuntu 16.04.6 LTS (GNU/Linux 4.19.0-8-amd64 x86_64) |
We are running the exact same Docker version on the same version on Ubuntu. Here is one of our bbb servers:
This is definitely some weird host thing. ls -l $(which python)
python3 --version |
(changed the default python library a few minutes ago from 2.7 to 3) |
You better change it back to 2.7 if it was present. Too many system scripts rely on that. In case it wasn't set it wouldn't be such big of an issue to change it. Did you try any of the previous commands with python->python3 ? If so, retry them. |
i did all of them with python2.7 and 3 on two different machines set up at the exact same time of the day. Everything is the same. :/
|
Did you change anything on the system? I see this is your bbb (and previously bbb2) host. If you tried on a different system with e.g. Ubuntu 18.04 this shouldnt occur. I'm trying on my mac and on our bbb server and I can't replicate your issue. How did you install docker? |
i didnt change anything on the system, it is a clean ubuntu 16.04 minimal inside a vm and setup using the bbb-install script. |
It's a shot in the dark, but could you try the docker command with the ubuntu user and not root? You will need to run with sudo. |
|
docker run --rm --entrypoint /usr/local/bin/python3 greenstatic/bigbluebutton-exporter:v0.2.0 server.py |
|
Okay now we are getting a permission error, this is getting stranger the deeper we go. Override the user of the container to root; sudo docker run --rm --user 0 --entrypoint /usr/local/bin/python3 greenstatic/bigbluebutton-exporter:v0.2.0 server.py |
Do you have selinux/apparmor or anything similar enabled? |
yes, apparmor is enabled. Overwriting user works!
|
Did you change your apparmor config besides the defaults? |
nope, i'm just starting to set up the servers, it is not modified, yet. |
I'll ask around a bit to see what other docker specialist think about this issue in the mean time I suggest you override the user (try first without entrypoint) in the docker-compose file. The user |
ok, i changed the docker-compose and now it is working (as a temporary workaround)
|
If you find anything regarding this, do share 😄 I'm completely stumped what the issue is 🤔 |
Did you by any chance solve the original issue? |
no, i didnt have any time to debug the initial issue and continued using the workaround |
Did you manage to solve your issue? |
its still the same |
i cannot start the bbb-exporter docker container.
The text was updated successfully, but these errors were encountered: