[prev in list] [next in list] [prev in thread] [next in thread]
List: lxc-users
Subject: [lxc-users] Re: [lxc-devel] lxc-create failure
From: Saint Michael <venefax () gmail ! com>
Date: 2023-07-08 17:47:35
Message-ID: CAC9cSOCs_+=4d61=WAo8_XBHT54rnAOe4LN==+1gbiz5QHSkow () mail ! gmail ! com
[Download RAW message or body]
Just in case somebody needs to create a new container: you can install the
package lxc-templates (debian) and install the container from a local copy.
Unless there are some distributions whose templates are only found online.
On Sat, Jul 8, 2023 at 1:19 PM Serge E. Hallyn <serge@hallyn.com> wrote:
> On Sat, Jul 08, 2023 at 10:11:31AM -0500, Serge E. Hallyn wrote:
> > On Sat, Jul 08, 2023 at 02:01:20AM -0700, Mark Grant wrote:
> > >
> > > This may be the wrong mailing list for this subject, if so I would
> > > appreciate a pointer to the correct place.
> > >
> > > Since yesterday I have received the following error messages when
> trying to
> > > create a Debian Bullseye or Bookworm amd64 container on a fresh or
> cached
> > > download:-
> > > Unpacking the rootfs
> > > ERROR: meta tarball is missing the configuration file
> > > lxc-create: debian-bullseye-dev: lxccontainer.c: create_run_template:
> 1616
> > > Failed to create container from template
> > > lxc-create: debian-bullseye-dev: tools/lxc_create.c: main: 319 Failed
> to
> > > create container debian-bullseye-dev
> > >
> > > The contents of the cache directory is:-
> > > mgrantprg@leonidas:~/.cache/lxc/download/debian/bullseye/amd64/default$
> ls
> > > -lh
> > > total 75M
> > > -rw-r--r-- 1 mgrantprg mgrantprg 15 Jul 8 09:46 build_id
> > > -rw-r--r-- 1 mgrantprg mgrantprg 166 Jul 8 06:28 create-message
> > > -rw-r--r-- 1 mgrantprg mgrantprg 1 Jul 8 06:28 excludes-user
> > > -rw-r--r-- 1 mgrantprg mgrantprg 11 Jul 8 06:28 expiry
> > > -rw-r--r-- 1 mgrantprg mgrantprg 75M Jul 8 07:14 rootfs.tar.xz
> > > mgrantprg@leonidas:~/.cache/lxc/download/debian/bullseye/amd64/default$
>
> > >
> > > The contents of a much older container for buster shows:-
> > > mgrantprg@leonidas:~/.cache/lxc/download/debian/buster/amd64/default$
> ls -lh
> > > total 67M
> > > -rw-r--r-- 1 mgrantprg mgrantprg 15 May 5 15:52 build_id
> > > -rw-r--r-- 1 mgrantprg mgrantprg 65 May 5 06:28 config
> > > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.1
> > > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.2
> > > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.3
> > > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.4
> > > -rw-r--r-- 1 mgrantprg mgrantprg 111 May 5 06:28 config-user
> > > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.1
> > > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.2
> > > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.3
> > > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.4
> > > -rw-r--r-- 1 mgrantprg mgrantprg 164 May 5 06:28 create-message
> > > -rw-r--r-- 1 mgrantprg mgrantprg 1 May 5 06:28 excludes-user
> > > -rw-r--r-- 1 mgrantprg mgrantprg 11 May 5 06:28 expiry
> > > -rw-r--r-- 1 mgrantprg mgrantprg 67M May 5 07:10 rootfs.tar.xz
> > > -rw-r--r-- 1 mgrantprg mgrantprg 25 May 5 06:28 templates
> > > mgrantprg@leonidas:~/.cache/lxc/download/debian/buster/amd64/default$
> > >
> > > I hope you can help.
> >
> > Hey,
> >
> > I assume this is a result of the infrastructure changes which are in
> > progress to effect the move of lxd (see https://linuxcontainers.org/lxd/
> > in case you haven't seen it). I unfortunately don't have any access
> > to the infrastructure so I can't help. I'm pretty sure Stéphane has
> > had his hands full with that move, so I'm afraid we need to give him
> > some time to get to fixing that.
> >
> > What's impressive to me is how long he has run that infrastructure with
> > nary a glitch, that its failure now is so painful :)
> >
> > -serge
>
> https://github.com/lxc/distrobuilder/pull/747
>
> CI needs to do its thing, but fixed images should start rolling out
> eventually.
>
--
You received this message because you are subscribed to the Google Groups "lxc-users" \
group. To unsubscribe from this group and stop receiving emails from it, send an \
email to lxc-users+unsubscribe@lists.linuxcontainers.org. To view this discussion on \
the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/ \
CAC9cSOCs_%2B%3D4d61%3DWAo8_XBHT54rnAOe4LN%3D%3D%2B1gbiz5QHSkow%40mail.gmail.com.
[Attachment #3 (text/html)]
<div dir="ltr"><div class="gmail_default" style="font-size:small">Just in case \
somebody needs to create a new container: you can install the package lxc-templates \
(debian) and install the container from a local copy.</div><div class="gmail_default" \
style="font-size:small">Unless there are some distributions whose templates are only \
found online.</div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Sat, Jul 8, 2023 at 1:19 PM Serge E. Hallyn <<a \
href="mailto:serge@hallyn.com">serge@hallyn.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">On Sat, Jul 08, 2023 at 10:11:31AM -0500, Serge E. \
Hallyn wrote:<br> > On Sat, Jul 08, 2023 at 02:01:20AM -0700, Mark Grant \
wrote:<br> > > <br>
> > This may be the wrong mailing list for this subject, if so I would <br>
> > appreciate a pointer to the correct place.<br>
> > <br>
> > Since yesterday I have received the following error messages when trying to \
<br> > > create a Debian Bullseye or Bookworm amd64 container on a fresh or \
cached <br> > > download:-<br>
> > Unpacking the rootfs<br>
> > ERROR: meta tarball is missing the configuration file<br>
> > lxc-create: debian-bullseye-dev: lxccontainer.c: create_run_template: 1616 \
<br> > > Failed to create container from template<br>
> > lxc-create: debian-bullseye-dev: tools/lxc_create.c: main: 319 Failed to \
<br> > > create container debian-bullseye-dev<br>
> > <br>
> > The contents of the cache directory is:-<br>
> > mgrantprg@leonidas:~/.cache/lxc/download/debian/bullseye/amd64/default$ ls \
<br> > > -lh<br>
> > total 75M<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 15 Jul 8 09:46 build_id<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 166 Jul 8 06:28 create-message<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 1 Jul 8 06:28 excludes-user<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 11 Jul 8 06:28 expiry<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 75M Jul 8 07:14 rootfs.tar.xz<br>
> > mgrantprg@leonidas:~/.cache/lxc/download/debian/bullseye/amd64/default$ \
<br> > > <br>
> > The contents of a much older container for buster shows:-<br>
> > mgrantprg@leonidas:~/.cache/lxc/download/debian/buster/amd64/default$ ls \
-lh<br> > > total 67M<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 15 May 5 15:52 build_id<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 65 May 5 06:28 config<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.1<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.2<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.3<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 72 May 5 06:28 config.4<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 111 May 5 06:28 config-user<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.1<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.2<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.3<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 125 May 5 06:28 config-user.4<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 164 May 5 06:28 create-message<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 1 May 5 06:28 excludes-user<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 11 May 5 06:28 expiry<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 67M May 5 07:10 rootfs.tar.xz<br>
> > -rw-r--r-- 1 mgrantprg mgrantprg 25 May 5 06:28 templates<br>
> > mgrantprg@leonidas:~/.cache/lxc/download/debian/buster/amd64/default$ <br>
> > <br>
> > I hope you can help.<br>
> <br>
> Hey,<br>
> <br>
> I assume this is a result of the infrastructure changes which are in<br>
> progress to effect the move of lxd (see <a \
href="https://linuxcontainers.org/lxd/" rel="noreferrer" \
target="_blank">https://linuxcontainers.org/lxd/</a><br> > in case you haven't \
seen it). I unfortunately don't have any access<br> > to the infrastructure \
so I can't help. I'm pretty sure Stéphane has<br> > had his hands full \
with that move, so I'm afraid we need to give him<br> > some time to get to \
fixing that.<br> > <br>
> What's impressive to me is how long he has run that infrastructure with<br>
> nary a glitch, that its failure now is so painful :)<br>
> <br>
> -serge<br>
<br>
<a href="https://github.com/lxc/distrobuilder/pull/747" rel="noreferrer" \
target="_blank">https://github.com/lxc/distrobuilder/pull/747</a><br> <br>
CI needs to do its thing, but fixed images should start rolling out<br>
eventually.<br>
</blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups \
"lxc-users" group.<br /> To unsubscribe from this group and stop receiving \
emails from it, send an email to <a \
href="mailto:lxc-users+unsubscribe@lists.linuxcontainers.org">lxc-users+unsubscribe@lists.linuxcontainers.org</a>.<br \
/> To view this discussion on the web visit <a \
href="https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/CAC9cSOC \
s_%2B%3D4d61%3DWAo8_XBHT54rnAOe4LN%3D%3D%2B1gbiz5QHSkow%40mail.gmail.com?utm_medium=em \
ail&utm_source=footer">https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/l \
xc-users/CAC9cSOCs_%2B%3D4d61%3DWAo8_XBHT54rnAOe4LN%3D%3D%2B1gbiz5QHSkow%40mail.gmail.com</a>.<br \
/>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic