Date: Mon, 30 Oct 2017 07:50:27 +0000 From: Luke Crooks <luke@solentwholesale.com> To: freebsd@posteo.co Cc: freebsd-jail@freebsd.org Subject: Re: Updating jails base binaries Message-ID: <CAC0r6X-KGnkukCYB6rX25vEGAbSFnEuw2TGfQ7giKSrsDKyicA@mail.gmail.com> In-Reply-To: <515c9089dfd25ba38df586f1274ff97f@posteo.net> References: <515c9089dfd25ba38df586f1274ff97f@posteo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rami, https://www.freebsd.org/doc/handbook/jails-ezjail.html See section 14.6.4 It works very well, it will take a while to rebuild the base system. Once rebuilt you can then update all jail(s) you have, very painless process. Regards, -- Luke Crooks Solent Wholesale Carpets www.solentwholesale.com On Sun, Oct 29, 2017 at 12:15 AM, Rami <freebsd@posteo.co> wrote: > > > Hi everyone, > I have an issue which I got aware of by accident couple of days ago > while I was upgrading a port in the jail. > I have a jail created using ezjail and running Gitea port in it. > Recently Gitea got updated so after upgrading the installed port in the > jail, the service started complaining as below > > _~ # SERVICE GITEA START _ > > daemon: illegal option -- S > usage: daemon [-cfr] [-p child_pidfile] [-P supervisor_pidfile] > [-t title] [-u user] command arguments ... > > After a bit of investigating we figured out that the binaries in the > jail are behind the host (and the jail kernel release). please check > below > > The jail where the gitea is running > > # freebsd-version > 11.1-RELEASE-p2# uname -a > > #uname -a > FreeBSD git.jail 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 > 11:55:48 UTC 2017 > _ROOT@AMD64-BUILDER.DAEMONOLOGY.NET_:/usr/obj/usr/src/sys/GENERIC amd64 > > # sha256 /usr/sbin/daemon > SHA256 (/usr/sbin/daemon) = > 2f1d9b434cae89c67aefa9798b87fd97bcde2f70b2ba0140b7052ae6536aaf8a > > # /USR/SBIN/DAEMON > _USAGE: DAEMON [-CFR] [-P CHILD_PIDFILE] [-P SUPERVISOR_PIDFILE]_ [-T > TITLE] [-U USER] > COMMAND ARGUMENTS ... > > The host > > ~ % freebsd-version > 11.1-RELEASE-p2~ > > % UNAME -A > _FREEBSD SERVER-LINODE-1-GIT 11.1-RELEASE-P1 FREEBSD 11.1-RELEASE-P1 #0: > WED AUG 9 11:55:48 UTC 2017 > __ROOT@AMD64-BUILDER.DAEMONOLOGY.NET__:/USR/OBJ/USR/SRC/SYS/GENERIC > AMD64_~ > > % sha256 /usr/sbin/daemon > SHA256 (/usr/sbin/daemon) = > 2b029a5c274c6292870caf35470041c2553b768346bb001c97d447877bc9caf5~ > > % /USR/SBIN/DAEMON > _USAGE: DAEMON [-CFRS] [-P CHILD_PIDFILE] [-P SUPERVISOR_PIDFILE]__ [-U > USER] [-O OUTPUT_FILE] [-T TITLE]__ [-L SYSLOG_FACILITY] [-S > SYSLOG_PRIORITY]_ [-T SYSLOG_TAG] [-M OUTPUT_MASK] > _COMMAND ARGUMENTS ..._ > > I will always update the jails using > # EZJAIL-ADMIN UPDATE -U > > and the ports > _# EZJAIL-ADMIN UPDATE -P_ > so it seems the kernel been updated yet not the binaries.... can anyone > please advise me to what is the best way to keep the whole system > kernel, base, and ports up to date in the jail (and keep the base > binaries and kernel match the same release) > > Thanks so much > Rami > > > _______________________________________________ > freebsd-jail@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-jail > To unsubscribe, send any mail to "freebsd-jail-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC0r6X-KGnkukCYB6rX25vEGAbSFnEuw2TGfQ7giKSrsDKyicA>