xpra icon
Bug tracker and wiki

Changes between Version 19 and Version 20 of Usage/Docker


Ignore:
Timestamp:
01/11/17 14:16:35 (3 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Usage/Docker

    v19 v20  
    33
    44The information below has not been verified by xpra.org, use at your own risk.
     5
     6
     7[[BR]]
    58
    69{{{#!div class="box"
     
    3841[[BR]]
    3942
    40 In the following solutions, xpra needs to connect to the xpra server running inside the docker container.
    41 Your options are:
    42 * using a TCP socket or running an SSH server in the container - neither are very practical
    43 * sharing the xpra socket directory between the host and the container. To do this you have multiple options:
     43== Sockets Access ==
     44
     45The xpra client needs to connect to the xpra server running inside the docker container. To do so, you can:
     46* use a TCP socket or run an SSH server in the container - neither are very practical
     47* share the xpra socket directory between the host and the container. To do this you have multiple options:
    4448 * bind mount the directory containing the socket ({{{.xpra}}} or {{{/tmp}}} usually)
    4549 * use the {{{socket-dir}}} option at either end to point to the same location
    46  * you could also create symlinks to individual sockets, but this can get messy very quickly
     50 * create symlinks to individual sockets, but this can get messy very quickly
    4751
    48 Xpra uses the hostname as part of the unix domain socket name.
     52By default, Xpra uses the hostname as part of the unix domain socket name.
    4953If the hostname is different inside the container, you will need one of those workarounds:
     54* specify the socket filename to use explicitly with {{{--bind=/path/to/socketname}}}
    5055* symlink or bind mount the server's unix domain socket if that's what you want to use to connect
    51 * you can connect to a specific unix domain socket by path using:
     56* you can also connect to a specific unix domain socket by path using:
    5257{{{
    5358xpra attach socket:/path/to/yourcontainers/socket
    5459}}}
    55 For older versions, you can override the hostname used with the environment variable {{{XPRA_SOCKET_HOSTNAME}}}, ie: {{{XPRA_SOCKET_HOSTNAME=myhostname xpra attach}}}
    56 
    5760
    5861----
    5962
    60 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)
    61 As of version 1.0, you can also specify the absolute path to the mmap file:
     63== mmap ==
     64
     65In 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.
     66So 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)
     67
     68Alternatively, you can also specify the absolute path to the mmap file:
    6269{{{
    6370xpra attach --mmap=/path/to/desired/mmapfile