Date: Tue, 23 Dec 2025 10:52:37 -0800 From: James Gritton <jamie@freebsd.org> To: freebsd-questions@freebsd.org Cc: Graham Menhennitt <graham@menhennitt.com.au> Subject: Re: error creating thin jail on 15.0 Message-ID: <4f56394c9bc2dd4aef5f426eda9679f0@freebsd.org> In-Reply-To: <e0af9569-47a8-482f-bafc-783f69935ac3@menhennitt.com.au> References: <e0af9569-47a8-482f-bafc-783f69935ac3@menhennitt.com.au>
index | next in thread | previous in thread | raw e-mail
On 2025-12-22 21:40, Graham Menhennitt wrote: > Hello, > > I've recently upgraded my server from 14.3 to 15.0. Everything appeared > to work successfully in the upgrade. > > I now want to create a thin jail using UFS. I've followed the handbook > section 17.5 exactly except that my jail is named "vaultwarden" instead > of "thinjail". Accordingly, I've replaced "thinjail" by "vaultwarden" > everywhere. > > When I try to start the jail, I get an error: > > # service jail start vaultwarden > Starting jails: cannot start jail "vaultwarden": > jail: vaultwarden: mount.devfs: > /usr/local/jails/containers/vaultwarden/dev: No such file or directory > . > # > > I tried creating directory /usr/local/jails/containers/vaultwarden/dev. > Then I get a different error: > > # service jail start vaultwarden > Starting jails: cannot start jail "vaultwarden": > 1 > jail: vaultwarden: /bin/sh /etc/rc: failed > . > # > > I'm completely new to jails. Can somebody please give me a clue on how > to diagnose then problem. Considering /dev didn't exist in the jail directory, I'm guessing that nothing exist there. That leaves two possibilities: the files weren't extracted into the master directory, or they weren't reflected into the thin jail directory. What it look like when you run: ls -l /usr/local/jails/templates/15.0-RELEASE ls -l /usr/local/jails/containers/vaultwarden Both of those directories should show a root directory listing. If the first one isn't there, something went wrong in downloading and unpacking the base file set. I would imagine there'd be some kind of error message if that were the case. If the second one isn't there, the clone didn't work. Again, I'd expect an error message. If both of them *do* show files, there's probably something wrong in the jail.conf. Another command with potentially useful output is "zfs list -t all". I would expect to see a line showing the dataset named zroot/jails/containers/vaultwarden at the mount point /usr/local/jails/containers/vaultwarden. - Jamiehelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f56394c9bc2dd4aef5f426eda9679f0>