From owner-freebsd-jail@freebsd.org Sat Dec 19 19:59:55 2015 Return-Path: Delivered-To: freebsd-jail@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22A74A4B979 for ; Sat, 19 Dec 2015 19:59:55 +0000 (UTC) (envelope-from trashcan@odo.in-berlin.de) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:d:3049:1:1:0:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E60811454 for ; Sat, 19 Dec 2015 19:59:54 +0000 (UTC) (envelope-from trashcan@odo.in-berlin.de) Received: from [IPv6:2003:45:483e:3a01:24d3:7330:5a82:c23e] (unknown [IPv6:2003:45:483e:3a01:24d3:7330:5a82:c23e]) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 3pNHw85KyQzDqR for ; Sat, 19 Dec 2015 20:59:52 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: iocage following stable? From: Michael Grimm In-Reply-To: <56748639.3040202@freebsd.org> Date: Sat, 19 Dec 2015 20:59:49 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <660A228D-5996-4C1C-BD27-D8BBBB8EDB23@odo.in-berlin.de> References: <56748639.3040202@freebsd.org> To: freebsd-jail@freebsd.org X-Virus-Scanned: clamav-milter 0.99 at mail.mer-waases.invalid X-Virus-Status: Clean X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2015 19:59:55 -0000 Allan Jude wrote: > On 2015-12-18 16:18, Michael Grimm wrote: >> I am running ezjail for some years now, but I intend to migrate to = iocage. Not that I am "disappointed" with ezjail, but I do want to give = VNET a try. >>=20 >> After having read iocage's documentation and some google research, I = am left with the following questions: >>=20 >> 1) Currently I am using ezjail's functionality to update/upgrade my = basejail from svn following STABLE. I am unsure if I can stick to = running STABLE in iocage jails, and if so, how? "iocage chroot" and = compile in /usr/src? >=20 > I don't know on this part Well, I did try that approach in the meantime, and yes, one might fake = iocage in this regard. >> 2) Is there an equivalent for "ezjail-admin console -e 'pkg upgrade = -y -f' jailname", namely running commands inside a jail without entering = it? >=20 > The generic jail command 'jexec' can work for this. >=20 > jexec pkg upgrade -y -f >=20 > Also, pkg itself has native support for jails. >=20 > pkg upgrade -j -y -f Thanks I didn't see the obvious :-( Thanks. After testing iocage today I do come to the conclusion that it does what = it is made for: perfect wrapper script for jail functionality. I did get = sam test jails running vnet, quite easily. But, I will not use iocage as a substitute for ezjail, not due to = lacking functionality, no en contre, rather due to "inflexibility" from = *my* point of view. Those UUIDs irritate me, and they make "zfs list" = rather "odd looking". And, I do miss "flexibility" regarding where to = nail "iocage" into my zpool filesystem. I am using beadm boot = environments, and I am used to stick ezjail's basejail to those. If = upgrading a basejail went wrong I will have a fallback basejail at hand. Anyway, I am currently testing jail management "the hard way" aka own = scripts ;-) Regards, Michael