[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
howtos:misc:lxc [2018/10/19 22:01 (UTC)] – [Custom Container Boot Process] mralk3howtos:misc:lxc [2019/12/28 02:27 (UTC)] – Add running GUI applications montagdude
Line 156: Line 156:
  
 Note that the second path intentionally lacks a leading slash. This is because it is a relative path -- relative to the container's rootfs. Once you start the container again and log in, you should see that the directory has been mounted at /home/container_user/foo. In general, it is best if the username on the host is the same as the container's username, because it avoids any conflicts in file ownership between the host and container user. Note that the second path intentionally lacks a leading slash. This is because it is a relative path -- relative to the container's rootfs. Once you start the container again and log in, you should see that the directory has been mounted at /home/container_user/foo. In general, it is best if the username on the host is the same as the container's username, because it avoids any conflicts in file ownership between the host and container user.
 +
 +==== Running GUI Applications ====
 +
 +Without taking additional steps, it will not be possible to run GUI applications installed in the container. The simplest way to accomplish this is to run them using SSH with X forwarding to the host. However, there are still a few steps required to make this happen. In the container, in /etc/ssh/sshd_config, set the following:
 +
 +<code>
 +X11Forwarding yes                                                                                                                      
 +X11UseLocalhost yes
 +</code>
 +
 +This will allow X forwarding via SSH from the container. (Note: X11UseLocalhost yes is required; otherwise X will give an error about the DISPLAY not existing.) It is also necessary to bind-mount the host's /tmp/.X11-unix directory in the container. Add this line to the container's config file ($lxcpath/container_name/config):
 +
 +<code>
 +lxc.mount.entry = /tmp/.X11-unix tmp/.X11-unix none bind,optional,create=dir
 +</code>
 +
 +Next, restart the container. Upon restart, use `lxc-ls --fancy` to determine the container's IP address. You can then run GUI apps from the container as follows:
 +
 +<code>
 +ssh -Y user@IP appname
 +</code>
 +
 +This is probably the simplest way to run GUI apps in the container. However, more advanced usage is possible, including using LXC to "sandbox" applications in an unprivileged container and/or running GUI applications directly in the container without connecting over SSH. For more information, the following page is a good start:
 +
 +[[https://stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/|LXC 1.0: GUI in containers [9/10]]]
  
 ====== See Also ====== ====== See Also ======
Line 166: Line 191:
  
 [[https://www.linuxquestions.org/questions/slackware-14/starting-lxc-container-in-slackware-14-2-a-4175614421/|LQ thread]] [[https://www.linuxquestions.org/questions/slackware-14/starting-lxc-container-in-slackware-14-2-a-4175614421/|LQ thread]]
 +
 +[[https://stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/|LXC 1.0: GUI in containers [9/10]]]
  
 ====== Sources ====== ====== Sources ======

Trace:

howtos:misc:lxc ()