Changes between Version 19 and Version 20 of Usage/Docker

Timestamp:

01/11/17 14:16:35 (3 years ago)

Author:

Antoine Martin

Comment:

--

Usage/Docker

@@ -3 +3 @@
 
 The information below has not been verified by xpra.org, use at your own risk.
+
+
+[[BR]]
 
 {{{#!div class="box"
@@ -38 +41 @@
 [[BR]]
 
-In the following solutions, xpra needs to connect to the xpra server running inside the docker container.
-Your options are:
-* using a TCP socket or running an SSH server in the container - neither are very practical
-* sharing the xpra socket directory between the host and the container. To do this you have multiple options:
+== Sockets Access ==
+
+The xpra client needs to connect to the xpra server running inside the docker container. To do so, you can:
+* use a TCP socket or run an SSH server in the container - neither are very practical
+* share the xpra socket directory between the host and the container. To do this you have multiple options:
  * bind mount the directory containing the socket ({{{.xpra}}} or {{{/tmp}}} usually)
  * use the {{{socket-dir}}} option at either end to point to the same location
- * you could also create symlinks to individual sockets, but this can get messy very quickly
+ * create symlinks to individual sockets, but this can get messy very quickly
 
-Xpra uses the hostname as part of the unix domain socket name.
+By default, Xpra uses the hostname as part of the unix domain socket name.
 If the hostname is different inside the container, you will need one of those workarounds:
+* specify the socket filename to use explicitly with {{{--bind=/path/to/socketname}}}
 * symlink or bind mount the server's unix domain socket if that's what you want to use to connect
-* you can connect to a specific unix domain socket by path using:
+* you can also connect to a specific unix domain socket by path using:
 {{{
 xpra attach socket:/path/to/yourcontainers/socket
 }}}
-For older versions, you can override the hostname used with the environment variable {{{XPRA_SOCKET_HOSTNAME}}}, ie: {{{XPRA_SOCKET_HOSTNAME=myhostname xpra attach}}}
-
 
 ----
 
-In order to be able to use {{{mmap}}} acceleration, the server expects to find the mmap file in the exact same path that the client used to create it. So you must ensure that the path to the mmap file (by default found in {{{$TMPDIR}}}) is the same on the host and in the container. (again, bind mounting a directory solves this problem)
-As of version 1.0, you can also specify the absolute path to the mmap file:
+== mmap ==
+
+In order to be able to use {{{mmap}}} acceleration, the server expects to find the mmap file in the exact same path that the client used to create it.
+So you must ensure that the path to the mmap file (by default found in {{{$TMPDIR}}}) is the same on the host and in the container. (again, bind mounting a directory solves this problem)
+
+Alternatively, you can also specify the absolute path to the mmap file:
 {{{
 xpra attach --mmap=/path/to/desired/mmapfile