-
Notifications
You must be signed in to change notification settings - Fork 34
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
Failed to launch the emulated environment: chroot: failed to run command 'bin/bash': Exec format error #6
Comments
Hey, do you have qemu and qemu-user-static installed on your host? |
My host is:
I have installed
so now I get errors when I am actually inside the emulated environment:
Assuming that this is my problem, any suggestions on how to install |
Hmm, are you running Docker for Mac or using Kitematic (or some other On 30 August 2016 at 10:46, Andrea Cortis notifications@github.com wrote:
|
I am running docker for Mac
Running the daemon
|
So the problem might be that docker runs in another host on OSX. I don't think qemu is required on the OSX machine, but it is required on whatever is running the docker environment. With the Docker for Mac application I don't think you should have to (or be able to) use docker-machine to control the docker host, and the instance they spin up works with qemu on the couple of OSX machines I have tested. It might be worth checking what is going on there (docker icon in top bar, definitely running, nothing running in docker-machine |
I have reinstalled Docker with Docker for Mac. And now the issue I originally reported is resolved. There is however still something that I do not understand (please tell me if you want me to open another issue). I cannot get an IP address in the emulated session (see below). Is that normal?
|
Good good ^_^ That is normal. Qemu isn't actually running the whole OS, only interpreting the binaries you call in the container. If you want to connect to it (ie. you are running a web server in the emulated environment) use the address of the docker host as above, and outbound things should /just work/ via the container. |
I am having an issue with launching the emulated CLI. Could you please advise?
Thanks
Andrea
The text was updated successfully, but these errors were encountered: