On 03/18/2019 09:32 PM, Gordon Messmer wrote:> On 3/18/19 6:05 PM, H wrote: >> Thank you, visited that page and tried the above but get the following messages: >> >> No protocol specified >> Geany: cannot open display > > > Can you copy the text of the command you ran and its output from your terminal, and paste that in a reply email? > > Also, run the command a second time, but add "echo -- " at the beginning so you can see how variables are expanded.? Include that command and output in your reply. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centosThink I got it to work now, I needed to add the RUN export ... at the page you linked to. I can now get geany to open, have not yet figured out how to be able to access files on the host computer...
On 3/18/19 6:39 PM, H wrote:> Think I got it to work now, I needed to add the RUN export ... at the page you linked to.Running "export" in your Dockerfile won't change the image that gets built. I tried running geany in a container on Fedora and had to make two adjustments.? First, the Fedora SELinux policy blocks access to /tmp/.X11-unix, and second I had to enable local connections using xhost, so: $ sudo setenforce permissive $ xhost +local:docker $ docker run -i -t --rm -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v ~/Documents:/root/Documents centos:7 /bin/bash --login [root at 45fdbee081d2 /]# yum -y install epel-release > /dev/null 2>&1 [root at 45fdbee081d2 /]# yum -y install geany > /dev/null 2>&1 [root at 45fdbee081d2 /]# geany $ sudo setenforce enforcing> I can now get geany to open, have not yet figured out how to be able to access files on the host computer...You'd use docker-run's "-v" flag to bind-mount the directory containing your files in the container, as I mounted my Documents directory above.? Take a look at the "docker-run" man page and check the documentation for each of the flags used in that command, at a minimum.
On 03/18/2019 10:57 PM, Gordon Messmer wrote:> On 3/18/19 6:39 PM, H wrote: >> Think I got it to work now, I needed to add the RUN export ... at the page you linked to. > > > Running "export" in your Dockerfile won't change the image that gets built. > > I tried running geany in a container on Fedora and had to make two adjustments.? First, the Fedora SELinux policy blocks access to /tmp/.X11-unix, and second I had to enable local connections using xhost, so: > > $ sudo setenforce permissive > $ xhost +local:docker > $ docker run -i -t --rm -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v ~/Documents:/root/Documents centos:7 /bin/bash --login > [root at 45fdbee081d2 /]# yum -y install epel-release > /dev/null 2>&1 > [root at 45fdbee081d2 /]# yum -y install geany > /dev/null 2>&1 > [root at 45fdbee081d2 /]# geany > $ sudo setenforce enforcing > > >> I can now get geany to open, have not yet figured out how to be able to access files on the host computer... > > > You'd use docker-run's "-v" flag to bind-mount the directory containing your files in the container, as I mounted my Documents directory above.? Take a look at the "docker-run" man page and check the documentation for each of the flags used in that command, at a minimum. > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centosGot it working, turned out all I had to do was to add another volume that is my home directory on the host computer. This relies on having the same user in both docker and on host computer.