Solved X11 socket vanishes after onestop/onestart the jail

[Holger]

I have a jail called “rockpro64-sdk” into which I mount the directory containing the X11 unix domain socket via an fstab file:

/tmp/.X11-unix          /jail/rockpro64-sdk/tmp/.X11-unix      nullfs         rw        0       0

After the following sequence of commands on the host the X11 socket in /tmp/.X11-unix vanishes both on the host and inside the jail:

# service jail onestop rockpro64-sdk
# service jail onestart rockpro64-sdk

After that the X-server still runs but I can (understandably) no longer start any applications, because they cannot communicate with the X-server.

What is going on here?

Here is my full jail config from /etc/jail.conf:

rockpro64-sdk {
        host.hostname="rockpro64-sdk.schattenwelt.org";
        ip4="inherit";
        ip6="inherit";
        path="/jail/rockpro64-sdk";
        mount.devfs;
        allow.raw_sockets=1;
        allow.chflags=1;
        exec.clean;
        exec.start="sh /etc/rc";
        exec.stop="sh /etc/rc.shutdown";
        mount.fstab="/jail/rockpro64-sdk/etc/fstab.jail";
}

 

[DtxdF]

In the jail's rc.conf(5) file:

clear_tmp_X="NO"

# or
#clear_tmp_enable="NO"

 

[NapoleonWils0n]

dont use an fstab with a jail

i found that using an fstab and then stopping the jail
resulted in the mountpoints not being unmounted

the solution is to put the mount points in the jails config
that way the jail "knows" about the mountpoints and they will be unmounted when you stop the jail

Chapter 17. Jails and Containers

Jails improve on the concept of the traditional chroot environment in several ways

docs.freebsd.org

 

[DtxdF]

dont use an fstab with a jail

i found that using an fstab and then stopping the jail
resulted in the mountpoints not being unmounted

the solution is to put the mount points in the jails config
that way the jail "knows" about the mountpoints and they will be unmounted when you stop the jail

Chapter 17. Jails and Containers

Jails improve on the concept of the traditional chroot environment in several ways

docs.freebsd.org

You should use the mount.fstab option in your jail.conf(5) instead of the host's fstab(5).