Docker-OSX
Docker-OSX copied to clipboard
sickcodes
nohup: failed to run command 'Xvfb'
Hi, I'm trying to use the docker image sickcodes/docker-osx:naked-auto, but I obtain this error.
nohup: appending output to 'nohup.out' nohup: failed to run command 'Xvfb': No such file or directory
how can I solve this issue? how can I download an older version of this docker image? Thanks a lot
Same issue here
i built the docker-osk:naked image using the Dockerfile.naked here on the repo
nohup: appending output to 'nohup.out'
nohup: failed to run command 'Xvfb': No such file or directory
Hi, I'm trying to use the docker image sickcodes/docker-osx:naked-auto, but I obtain this error.
nohup: appending output to 'nohup.out' nohup: failed to run command 'Xvfb': No such file or directoryhow can I solve this issue? how can I download an older version of this docker image? Thanks a lot
solution here >> https://github.com/sickcodes/Docker-OSX/issues/498#issuecomment-1133786915
Hi, I'm trying to use the docker image sickcodes/docker-osx:naked-auto, but I obtain this error.
nohup: appending output to 'nohup.out' nohup: failed to run command 'Xvfb': No such file or directoryhow can I solve this issue? how can I download an older version of this docker image? Thanks a lot
solution here >>
https://github.com/sickcodes/Docker-OSX/issues/498#issuecomment-1133786915
Thank you very much. I'm testing images now
Did you manage to have any luck with the above solution? I'm still experiencing the error, but I can see this issue is still open :)
I compiled myself the docker image with the modification and it works. But I did not try the precompiled docker image
Given that i'll need this for CI, i'll wait for the precompiled images in that case, and just pray theres not something else fucked up with my CI setup 😄
the precompiled images are there...if you see the date of the image, it is after the commit https://hub.docker.com/layers/docker-osx/sickcodes/docker-osx/naked-auto/images/sha256-a9b9ad861dbd464206352bed403a66a14111ff0a2a965d3c0bde4cd47fdd48b6?context=explore
@manang thanks for that! Looks like there might still be a problem then, because i'm still seeing the above issue