- #DOCKER FOR MAC GENERAL SETTING HOW TO#
- #DOCKER FOR MAC GENERAL SETTING INSTALL#
- #DOCKER FOR MAC GENERAL SETTING SOFTWARE#
- #DOCKER FOR MAC GENERAL SETTING CODE#
This is where the X server is running: $ ifconfigĭocker0 Link encap:Ethernet HWaddr 56:84:7a:fe:97:99 This creates a new 800圆00 window, which acts as a X server.įind an "external" address of your machine. Run Xephyr: $ Xephyr -ac -br -noreset -screen 800圆00 -host-cursor :1
#DOCKER FOR MAC GENERAL SETTING INSTALL#
Install Xephyr: $ sudo apt-get install xserver-xephyr
#DOCKER FOR MAC GENERAL SETTING HOW TO#
This is not necessary, but most linux desktops do not allow running remote apps on them by default ( here's how to "fix" this on ubuntu). I managed to run xeyes in a container and see the "window" in a X server running outside of the container. Run VNC within the container, and connect to it from the host with a VNC client.īetween those two options, I would recommend the first, but see which works best for your situation.
Run sshd within the container, turn on X11 forwarding, and then connect to the container using ssh -X (more secure) or ssh -Y (less secure, used only if you fully trust the containerized application). YMMV, and you may get lucky, but if you are looking to run a Qt-based application from within a Docker container, you may have to go the "old-fashioned" approach and either
#DOCKER FOR MAC GENERAL SETTING CODE#
I say "probably" because I have not tested this approach with enough Qt applications to be sure, or dug into the Qt source code enough to figure out why this is not supported. X Error: BadDrawable (invalid Pixmap or Window parameter) 9 X Error: BadShmSeg (invalid shared segment parameter) 148 If you try running a QT-based application this way, you will probably get an error like the following: X Error: BadAccess (attempt to access private resource denied) 10 It turns out that Qt does not support sharing of X sessions in this way (or at least does not support it well). However, your answer asks about PyQT specifically. For example, if you try this with Firefox (which is GTK-based), it will work (note that if you are already running Firefox on the host, it will open a new window in the host rather than open a new instance of Firefox from within the container). This will work for applications such as xterm, as well as GTK-based applications. (I would also recommend passing the -u flag, as running X11 applications as root does not always work, and is generally not recommended, especially when sharing sessions). docker run -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=unix$DISPLAY TheImage The answer given by Nasser Alshammari is the simplest (and fastest) approach to running GTK applications inside a Docker container - simply mount the socket for the X server as a Docker volume and tell Docker to use that instead. The other answers are mostly correct, but with some caveats that I have learned the hard way, and I would like to save others trouble. Is it possible to use Docker to have a development/production environment for a GUI-based application (PyQt/QT)? If yes, what would be the first steps to approach that?Ĭurrently this question is not answered, but it is very highly ranked on Google.
#DOCKER FOR MAC GENERAL SETTING SOFTWARE#
I would like to try Docker to solve the problem, but I still do not know if it is possible to set up images/containers that allow for some GUI based software to operate.
The problem is that I have tried to use Chef, but it takes a lot of effort to actually maintain Chef knowledge and skills (we do not have a dedicated Ops guy) and moreover a Chef recipe can fail if some third party repository is no longer available (this is a main stopper). This client software is updated regularly and I would like to have some configuration/provisioning tool that allows to have the same environment on each machine and hence provide easy deployment and configuration of the software onto each of the clients' machines. Each machine runs identical software, which is a PyQT-based web client that connects to a server. I have a set of client machines that are a part of an enterprise web application.
0 kommentar(er)
