> >
> > but not on startup.
>
> This sounds like an issue with your distro's init/mountall. LXC is
> not involved with the container's /etc/fstab. So we'd need more
> information on the container distro+version for anyone to be able
> to help you.
>
It could also be related to a "wrong" boot ord
I run lxc container on centos and want to my container to start with a
> static IP address.
>
You can set the static IP directly in the lxc's config file:
lxc.network.ipv4 = 192.168.0.11/24
I don't run LXC on CentOS though, so I'm not 100% sure if it'll work. Try
it :)
__
On Mon, Apr 7, 2014 at 4:44 PM, Serge Hallyn wrote:
> Quoting Christoph Mitasch (cmita...@thomas-krenn.com)
>
> Hello Serge,
> >
> > thanks for feedback regarding the library. Is any development code for
> the library already available?
>
> See
>
> https://lists.linuxcontainers.org/pipermail/lxc-u
Hello all,
OS: Ubuntu 14.04.1 LTS
LXC Version: 1.0.6-0ubuntu0.1
Experienced a weird issue when I tried to launch a container which mounts
an additional logical volume (ext4 formatted) through the container's fstab
file:
# cat /var/lib/lxc/mycontainer/fstab
/dev/vglxc/apps mnt/apps ext4 ro 0 0
T
ote:
> Quoting Claudio Kuenzler (c...@claudiokuenzler.com):
> > Hello all,
> >
> > OS: Ubuntu 14.04.1 LTS
> > LXC Version: 1.0.6-0ubuntu0.1
> >
> > Experienced a weird issue when I tried to launch a container which mounts
> > an additional logical volu
reground mode.
lxc-start 1416996126.765 ERRORlxc_start_ui - lxc_start.c:main:346
- Additional information can be obtained by setting the --logfile and
--logpriority options.
Will try to redo this in a clean installation.
On Wed, Nov 26, 2014 at 7:31 AM, Claudio Kuenzler
wrote:
> I
Wed, Nov 26, 2014 at 11:19 AM, Claudio Kuenzler
wrote:
> I applied the patch but it does not work for the read only mount.
>
> lxc-start 1416993491.172 INFO lxc_conf -
> conf.c:check_autodev:3821 - Autodev not required.
> lxc-start 1416993491.172 ERRORlxc_conf -
of it,
> like nfs or aufs, and then mount that additional layer ro.
>
> --
> Fajar
>
>
> On Wed, Nov 26, 2014 at 7:29 PM, Claudio Kuenzler
> wrote:
>
>> I made a couple of mistakes in my modified patch - so please ignore
>> that.But the basic idea of it was to
Hello,
Been pulling my hair out (what's left of it) because a script basically
used for auto-re-creation of containers is working when I launch it
manually, but the very same script does not work when run by cron.
I narrowed it down to the "lxc-destroy" command which simply does not do
anything w
vars */]) = -1 ENOENT (No such file or directory)
execve("/sbin/lvremove", ["lvremove", "-f", "/dev/vglxc/mycontainer"], [/*
34 vars */]) = 0
brk(0) = 0x1a48000
[...]
--- % snip % ---
Loo
Have you tried this way:
echo "en_US.UTF-8 UTF-8" > /etc/locale.gen
locale-gen
It's the method we're using the set the locale in LXC containers.
On Sat, Mar 19, 2016 at 11:33 AM, wrote:
> None of the typical ways of setting locales seem to stick in my Ubuntu
> container in an Ubuntu host (Ubu
Please show your /etc/network/interfaces for more clues.
On Mon, Dec 19, 2016 at 1:34 PM, mierdatutis mi wrote:
> Hi,
> I've configured a container with ubuntu and my host with ubuntu also. My
> idea is that they are in same lan with statics ip's.
> For these I've configured macvlan.
>
> In my h
12 matches
Mail list logo