mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-11 21:10:25 +01:00
Fail to run Docker-OSX on Digital Ocean Ubuntu18.04&20.04&CentOS #247
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @guoguoguilai on GitHub (Sep 28, 2021).
After doing the inital step and reboot, the output remains still the same.
I also tried other image, and got no luck.
OS related issued, please help us identify the issue by posting the output of this
@sickcodes commented on GitHub (Sep 28, 2021):
Are you root? Do you have a desktop running?
I believe you're missing from the Docker group
@guoguoguilai commented on GitHub (Sep 28, 2021):
Yes, I am root. But I don't have a desktop running. Should I install gnome in my DO?
@guoguoguilai commented on GitHub (Sep 28, 2021):
After installing gnome, I still got no luck.
I am running on a clean Digital Ocean Droplet. Is there any tutorial on How to Run Docker-OSX On Digital Ocean? Or could anyone share a Custom Images of Droplets?
@sickcodes commented on GitHub (Sep 28, 2021):
This script is for Digital Ocean, CPU Optimized servers: https://github.com/sickcodes/Docker-OSX/blob/master/tests/test.sh
@guoguoguilai commented on GitHub (Sep 28, 2021):
Thank you. I will try it out. Can I use SHARED CPU server to run this script?
@sickcodes commented on GitHub (Sep 29, 2021):
I don't think it works, but I know the CPU optimized servers do :)
@sickcodes commented on GitHub (Oct 4, 2021):
I also got this error today, will figure out if I did anything wrong
@MaxPowerReforged commented on GitHub (Oct 4, 2021):
I am getting this error as well running locally on my machine, Manjaro with KDE desktop.
@MaxPowerReforged commented on GitHub (Oct 8, 2021):
In my case I was doing a silly mistake, I wasn't running the command as root, so just
sudo sufixed it. Just writing it in case somebody has the same problem.@corwin-of-amber commented on GitHub (Nov 4, 2021):
I am running with
sudo su, but still I getgtk initialization failed.Using Debian 10 with OpenBox desktop.
@corwin-of-amber commented on GitHub (Nov 4, 2021):
It seems like it was the
xhost +problem after all. I have set it but apparently only after having fiddled too much with theDISPLAYsetting. My X11 was running on display:1; soxhost +then running the command with-e "DISPLAY=:1"just works. What threw me off was that omitting the-e "DISPLAY=..."silences the errorClient cannot connect, and does not issue an error about an unsetDISPLAYvariable. But it does fail if it is not set.@sickcodes commented on GitHub (Nov 5, 2021):
Yeah I have it set so it will select :0 by default, if DISPLAY is unset.
@corwin-of-amber commented on GitHub (Nov 5, 2021):
Oh that does explain why there was no error for DISPLAY being missing. Dunno why there was no error about it trying to connect to a nonexistent display.