search

amcorreia / docker-teamviewer

MIT License
4 stars 2 forks source link

GUI does not starts #1

Open TerkiKerel opened 6 years ago

TerkiKerel commented 6 years ago

Hi,

I run this command but GUI never starts, I waited 7 minutes:

docker run -d -it --rm -v /tmp/.X11-unix:/tmp/.X11-unix --name teamviewer amcorreia/docker-teamviewer

docker logs --follow 

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:ole:CoGetClassObject class {4315d437-5b8c-11d0-bd3b-00a0c911ce86} not registered
err:ole:CoGetClassObject class {4315d437-5b8c-11d0-bd3b-00a0c911ce86} not registered
err:ole:CoGetClassObject no class object {4315d437-5b8c-11d0-bd3b-00a0c911ce86} could be created for context 0x3
wine: configuration in '/opt/teamviewer/profile' has been updated.
Launching TeamViewer ...
Starting network process (no daemon)
Network process started (209)
Launching TeamViewer GUI ...
amcorreia commented 6 years ago

Hi there,

With root user run: (Actually I think regular user is enough)

# xhost +
TerkiKerel commented 6 years ago

I started the container, I waited for 4-5 minutes and than I run this command outside of the container: xhost + it prints: access control disabled, clients can connect from any host

I try this as a regular user. But I try it also with "sudo" command, it prints the same output.

I try the command also before start the container. Nothing changed.

amcorreia commented 6 years ago

Yes, you should run xhost + before docker run..

Which OS are you using?

Also try this command

docker run -d -it --rm  -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=unix$DISPLAY  --name teamviewer amcorreia/docker-teamviewer
TerkiKerel commented 6 years ago

I am using Ubuntu 16.04.

I run your last script but the same things happened. Exactly the same log printed inside docker.

amcorreia commented 6 years ago

I think you need check if X server host socket is running in a different path, I don't have a Ubuntu right now to check.

-v /tmp/.X11-unix:/tmp/.X11-unix

This one.

TerkiKerel commented 6 years ago

@amcorreia what is the command? your last command start with "-v".

amcorreia commented 6 years ago

@TerkiKerel

I installed a Ubuntu 18.04 and worked fine, the only command I have to run before docker was

xhost +

then

docker run -it --rm -v /tmp/.X11-unix:/tmp/.X11-unix --name teamviewer amcorreia/docker-teamviewer

BTW: try this command, is better to see the error messages.

TerkiKerel commented 6 years ago

command: xhost + output: access control disabled, clients can connect from any host

command: docker run -it --rm -v /tmp/.X11-unix:/tmp/.X11-unix --name teamviewer amcorreia/docker-teamviewer output

Unable to find image 'amcorreia/docker-teamviewer:latest' locally
latest: Pulling from amcorreia/docker-teamviewer
9f0706ba7422: Pull complete 
5327d91f59c2: Pull complete 
Digest: sha256:daf77d22c17efe57df5b6f1d53f8a8d5131f21800f98cdff423ca6c99ba35bcf
Status: Downloaded newer image for amcorreia/docker-teamviewer:latest

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:ole:CoGetClassObject class {4315d437-5b8c-11d0-bd3b-00a0c911ce86} not registered
err:ole:CoGetClassObject class {4315d437-5b8c-11d0-bd3b-00a0c911ce86} not registered
err:ole:CoGetClassObject no class object {4315d437-5b8c-11d0-bd3b-00a0c911ce86} could be created for context 0x3
wine: configuration in '/opt/teamviewer/profile' has been updated.
Launching TeamViewer ...
Starting network process (no daemon)
Network process started (209)
Launching TeamViewer GUI ...

I wait about 10 minutes. Nothing happened.

hkominos commented 5 years ago

Same here. I see the teamviewer process running from within the container but no GUI is launched on my host .

After: echo $DISPLAY unix:0

I set DISPLAY to 0:0 I think. and restarted the TW process manually and it worked

jackTaw88 commented 5 years ago

@hkominos I have the same problem with @TerkiKerel.

How did you changed DISPLAY to 0:0. with which command did you do that? Inside container? Before run docker did you type a few commands? After run docker?