Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Aug 2019 13:57:00 +0200
From:      Alexander Leidinger <Alexander@leidinger.net>
To:        freebsd-current@freebsd.org
Subject:   Re: jails, ZFS, deprecated jail variables and poudriere problems
Message-ID:  <20190828135700.Horde.m2EjpS9j67KYn2E1oSeoK8f@webmail.leidinger.net>
In-Reply-To: <20190827101149.1efcb946@freyja>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
Quoting "O. Hartmann" <ohartmann@walstatt.org> (from Tue, 27 Aug 2019  
10:11:54 +0200):

> We have a single ZFS pool (raidz), call it pool00 and this pool00 conatins a
> ZFS dataset pool00/poudriere which we want to exclusively attach to a jail.
> pool00/poudriere contains a complete clone of a former, now decomissioned
> machine and is usable by the host bearing the jails. The jail, named  
> poudriere,
> has these config parameters set in /etc/jail.conf as recommended:
>
>         enforce_statfs=         "0";
>
>         allow.raw_sockets=      "1";
>
>         allow.mount=            "1";
>         allow.mount.zfs=        "1";

The line above is what is needed, and what is replacing the sysctl  
you've found.

>         allow.mount.devfs=      "1";
>         allow.mount.fdescfs=    "1";
>         allow.mount.procfs=     "1";
>         allow.mount.nullfs=     "1";
>         allow.mount.fusefs=     "1";
>
> Here I find the first confusing observation. I can't interact with  
> the dataset
> and its content within the jail. I've set the "jailed" property of
> pool00/poudriere via "zfs set jailed=on pool00/poudriere" and I also have to
> attach the jailed dataset manually via "zfs jail poudriere  
> pool00/poudriere" to
> the (running) jail. But within the jail, listing ZFS's mountpoints reveal:
>
> NAME                USED  AVAIL  REFER  MOUNTPOINT
> pool00             124G  8.62T  34.9K  /pool00
> pool00/poudriere   34.9K  8.62T  34.9K  /pool/poudriere
>
> but nothing below /pool/poudriere is visible to the jail. Being confused I

Please be more verbose what you mean by "interact" and "is visible".

Do zfs commands on the dataset work?

Note, I don't remember if you can manage the root of the jail, but at  
least subsequent jails should be possible to manage. I don't have a  
jail where the root is managed in the jail, just additional ones.  
Those need to have set a mountpoint after the initial jailing and then  
maybe even be mounted for the first time.

Please also check /etc/defaults/devfs.rules if the jail rule contains  
an unhide entry for zfs.

Bye,
Alexander.

-- 
http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABAgAGBQJdZmwMAAoJEBINsJsD+NiGKfUP/AwQiECsn5Os00z6O4rs2w6O
iU2o9NbgP6TLKgoTnPy/vTv4TwnzLBgMJCmX88ddQBRdoANaBASztfro1QpNzUim
Jpi1fNmmJW+LznskWYDWnEuPXVPUy645RgVUuTNTFOWcAh4438TgjJ0tc2IN2h+a
eq1GnfRPRnof4PLDdpbOS/IdjP/ujZj5yawK03fG3I36usWooIIRPWUbBFlpVh4R
Y6Yb4rZIWS6SAnbfzVFUQLx3TnglmnD84+NwkyDhDSObQwP/nPMwKByCE5QB/DhK
mz2l0mEYuGV/cPfgMA0QqSL5R+IKgtA/BQ4JvUzrwjQ6nSFpqZQlGE8v3cryajd7
YKcAp099qtHn9vHvhLfgMVLqt97ktaq9PPpMRt364Ir9UtzO1FuH8pnLhirJklgu
EAlrmGjd4RaYR1XFGcY6eIbNvnZm45nyMoZty3urqI11BTNeZ8Qqsn7RVbk+KQzq
inCgt0pWgkVgMXloXYzZ70pqgZEawT7Q4mNf1CXB+1DnQUhbFbu890CVtzM9HNmo
RwgpzB0jnq3LuqnRySv9xFD3odSJV+7N5qJm1gzyYuFOhKJMXbmtlMexfGN6qSuG
eLPkujWza4q1kHxbMIaeiBjtATolNTyj3MHHcIxJ7a8VFoCBVVWYiBz+JMdLNgEJ
9L0wnDXIVSqB7hy1UJ/y
=6y94
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190828135700.Horde.m2EjpS9j67KYn2E1oSeoK8f>