xpra icon
Bug tracker and wiki

Changes between Version 7 and Version 8 of Usage/Docker


Ignore:
Timestamp:
07/05/15 11:45:40 (4 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Usage/Docker

    v7 v8  
    3030* using a TCP socket or running an SSH server in the container - neither are very practical
    3131* sharing the xpra socket directory between the host and the container. To do this you have multiple options:
    32  * bind mount the {{{.xpra}}} directory
     32 * bind mount the directory containing the socket ({{{.xpra}}} or {{{/tmp}}} usually)
    3333 * use the {{{socket-dir}}} option at either end to point to the same location
    3434 * you could also create symlinks to individual sockets, but this can get messy very quickly
    3535
    36 If the hostname is different inside the container, you will need to symlink or bind mount the server's unix domain socket if that's what you want to use to connect. Alternatively, you can override the hostname used with the environment variable {{{XPRA_SOCKET_HOSTNAME}}}:
     36Xpra uses the hostname as part of the unix domain socket name.
     37If the hostname is different inside the container, you will need one of those workarounds:
     38* symlink or bind mount the server's unix domain socket if that's what you want to use to connect
     39* override the hostname used with the environment variable {{{XPRA_SOCKET_HOSTNAME}}}, ie:
    3740{{{
    3841XPRA_SOCKET_HOSTNAME=myhostname xpra attach
     42}}}
     43* starting with version 0.15.3, you can connect to a unix domain socket by path using:
     44{{{
     45xpra attach socket:/path/to/yourcontainers/socket
    3946}}}
    4047