Closed altano closed 5 years ago
Exit code 127 usually means that the command is not found.
I don't "add" the code in a very good place (just /root/
so if you are putting something on top of that, it will blow away the novnc stuff.
Here's what I did:
docker build --rm -t altano/wine-test:latest .
docker run --rm -p 8080:8080 altano/wine-test:latest
And I get the same error above. Meanwhile your image works fine.
Does the repo in exactly its current form actually work for you?
Can you show me the Dockerfile
for altano/wine-test
?
It’s the Dockerfile in this repo. I’m just building this repo. I was trying to do something custom before but now I’m just stuck getting this repo to work as is.
I've confirmed that master as-is does work. I've just pushed a change that sends stderr to the console too, but I expect it to say "command not found" (127)
If you can, run the container with -ti
and just run bash
and see if you can run vnc directly and skip supervisord? I think that will give you the "smoking gun"
https://github.com/solarkennedy/wine-x11-novnc-docker/blob/master/supervisord.conf#L19
Yeah, that immediately revealed the problem.
It broke because I was using Windows to build the Docker image and the git repo was checked out with everything converted to CRLF. https://github.com/solarkennedy/wine-x11-novnc-docker/pull/4
Thanks so much!
Hey @solarkennedy thanks for this cool image.
I think I'm hitting the same issue as in /issues/2. I can use your image directly and it works:
But if I build your image from the Dockerfile and run it I get errors:
Not sure what the issue is. Any ideas?