Re: [lxc-users] systemd and logging in containers

[Michael H. Warfield]

On Tue, 2014-06-10 at 16:51 -0400, Leonid Isaev wrote:
> Hi,
> 
> On Tue, Jun 10, 2014 at 03:43:12PM -0400, Michael H. Warfield wrote:
> > Date: Tue, 10 Jun 2014 15:43:12 -0400
> > From: "Michael H. Warfield" 
> > To: LXC users mailing-list 
> > Subject: Re: [lxc-users] systemd and logging in containers
> > X-Mailer: Evolution 3.10.4 (3.10.4-2.fc20)
> > 
> > On Tue, 2014-06-10 at 21:19 +0200, István Király wrote:
> > > Hi list, ..
> > 
> > > Fedora 20 host and containers.
> > 
> > > Some programms are logging normal, apache, mariadb, .. 
> > 
> > > But some others have no log at all, for example maillog is 0 in all my
> > > containers, but they have postfix / dovecot running.
> > 
> > > I experimented a little today, with a custom script echoing messages
> > > to standard output, and created a systemd unit file for it. ..
> > 
> > > When I run this script as service on the host, I get the messages from
> > > systemctl status test.service.
> > 
> > > When I run this script from a container, the messages are not in
> > > systemctl status, and I can't find them.
> > 
> > > Checked if maybe packages are missing, but all seems to be okay, ..
> > 
> > > .. anyone have any ideas?
> > 
> > Yes.
> > 
> > Several revs back on systemd, the systemd-journald.service was horribly
> > broken and, at random, eating CPU time for lunch, particularly in
> > containers.  That turned out to be a bug involving (iirc) logging
> > objects and object id's and user logs with conflicting ids.
> > 
> > During this period of time, I coded the Fedora template to disable and
> > mask systemd-journald.service.  They have since fixed this bug and I've
> > reenabled it in the template, but containers built prior to this will
> > have the systemd-journal service disabled and masked.

> I'm surprised it actually worked -- what systemd version was that?

It did at the time.  :-)=)  I don't recall the specific version but I
recall having a hell of a time with journald sucking down the CPU under
F18 and F19.

> I don't think you can 'disable' (stop) journal in new-ish systemd (i.e. >=210)
> because it is a core module, so the best you can do is to set Storage=none in
> journald.conf.

I'll have to look into that.

> HTH,

Thanks!

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 978-7061 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes we live in the best of all
 PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!



signature.asc
Description: This is a digitally signed message part
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] systemd and logging in containers

[Leonid Isaev]

Hi,

On Tue, Jun 10, 2014 at 03:43:12PM -0400, Michael H. Warfield wrote:
> Date: Tue, 10 Jun 2014 15:43:12 -0400
> From: "Michael H. Warfield" 
> To: LXC users mailing-list 
> Subject: Re: [lxc-users] systemd and logging in containers
> X-Mailer: Evolution 3.10.4 (3.10.4-2.fc20)
> 
> On Tue, 2014-06-10 at 21:19 +0200, István Király wrote:
> > Hi list, ..
> 
> > Fedora 20 host and containers.
> 
> > Some programms are logging normal, apache, mariadb, .. 
> 
> > But some others have no log at all, for example maillog is 0 in all my
> > containers, but they have postfix / dovecot running.
> 
> > I experimented a little today, with a custom script echoing messages
> > to standard output, and created a systemd unit file for it. ..
> 
> > When I run this script as service on the host, I get the messages from
> > systemctl status test.service.
> 
> > When I run this script from a container, the messages are not in
> > systemctl status, and I can't find them.
> 
> > Checked if maybe packages are missing, but all seems to be okay, ..
> 
> > .. anyone have any ideas?
> 
> Yes.
> 
> Several revs back on systemd, the systemd-journald.service was horribly
> broken and, at random, eating CPU time for lunch, particularly in
> containers.  That turned out to be a bug involving (iirc) logging
> objects and object id's and user logs with conflicting ids.
> 
> During this period of time, I coded the Fedora template to disable and
> mask systemd-journald.service.  They have since fixed this bug and I've
> reenabled it in the template, but containers built prior to this will
> have the systemd-journal service disabled and masked.

I'm surprised it actually worked -- what systemd version was that?

I don't think you can 'disable' (stop) journal in new-ish systemd (i.e. >=210)
because it is a core module, so the best you can do is to set Storage=none in
journald.conf.

HTH,
-- 
Leonid Isaev
GPG fingerprints: DA92 034D B4A8 EC51 7EA6  20DF 9291 EE8A 043C B8C4
  C0DF 20D0 C075 C3F1 E1BE  775A A7AE F6CB 164B 5A6D


pgpnypIE2Vq98.pgp
Description: PGP signature
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] systemd and logging in containers

[Michael H. Warfield]

On Tue, 2014-06-10 at 21:19 +0200, István Király wrote:
> Hi list, ..

> Fedora 20 host and containers.

> Some programms are logging normal, apache, mariadb, .. 

> But some others have no log at all, for example maillog is 0 in all my
> containers, but they have postfix / dovecot running.

> I experimented a little today, with a custom script echoing messages
> to standard output, and created a systemd unit file for it. ..

> When I run this script as service on the host, I get the messages from
> systemctl status test.service.

> When I run this script from a container, the messages are not in
> systemctl status, and I can't find them.

> Checked if maybe packages are missing, but all seems to be okay, ..

> .. anyone have any ideas?

Yes.

Several revs back on systemd, the systemd-journald.service was horribly
broken and, at random, eating CPU time for lunch, particularly in
containers.  That turned out to be a bug involving (iirc) logging
objects and object id's and user logs with conflicting ids.

During this period of time, I coded the Fedora template to disable and
mask systemd-journald.service.  They have since fixed this bug and I've
reenabled it in the template, but containers built prior to this will
have the systemd-journal service disabled and masked.

In the container...

systemctl unmask systemd-journald.service
systemctl start systemd-journald.service

That should start journaling.  You may also have to restart your various
services or restart the container.  I've had varying success.  Quite
frankly, syslog (rsyslog) made so much more sense.

You should not need to "enable" systemd-journald.service as it's a
"socket started" service.

> Thank you.

Regards,
Mike

> 
> -- 
> Király István
> +36 209 753 758
> lak...@d250.hu
> 
> 
> 
> -- 
> This message has been scanned for viruses and 
> dangerous content by MailScanner, and is 
> believed to be clean. 
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users

-- 
Michael H. Warfield (AI4NB) | (770) 978-7061 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes we live in the best of all
 PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!



signature.asc
Description: This is a digitally signed message part
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] systemd and logging in containers

[István Király]

Hi list, ..

Fedora 20 host and containers.

Some programms are logging normal, apache, mariadb, ..

But some others have no log at all, for example maillog is 0 in all my
containers, but they have postfix / dovecot running.

I experimented a little today, with a custom script echoing messages to
standard output, and created a systemd unit file for it. ..

When I run this script as service on the host, I get the messages from
systemctl status test.service.

When I run this script from a container, the messages are not in systemctl
status, and I can't find them.

Checked if maybe packages are missing, but all seems to be okay, ..

.. anyone have any ideas?

Thank you.

-- 
Király István
+36 209 753 758
lak...@d250.hu

___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] ssh is stopped under unprivileged container

[Maxim DEMENTIEV]

Hi All,

I'm using an unprivileged container by running:

lxc-start -n z1 -- env -i HOME=/root TERM=xterm /bin/bash --login -i

And I've got problem. When I run ssh and it asks for a password (be it ssh
or ssh-add) the program immediately stops:

# ssh {host}
mdementiev@{host}'s password:

[1]+  Stopped ssh {host}
#

I don't have this problem if I run the same under lxc-usernsexec + chroot.

Host system:  Ubuntu 14.04 LTS (GNU/Linux 3.13.0-24-generic x86_64)
LXC: 1.0.3

Regards,
Max
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Networking in LXC

[Fajar A. Nugraha]

On Tue, Jun 10, 2014 at 6:39 PM, Ajith Adapa  wrote:
> Thanks for the reply @Fajar.
>
> (From Host)
> # lxc-attach -n root -- echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
>
> (Inside container)
> # ifconfig
> -bash: ifconfig: command not found
> # echo $PATH
> /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin

That is odd. ifconfig should be on /sbin/ifconfig. And /sbin is in
your path inside the container. Not sure what's wrong.

>
> As you mentioned there is a difference in PATH. I am using default
> config to create a lxc container. Is it an issue with fedora or we
> have to manually set it everytime a container is created ?


My best suggestion would be to try lxc-1.0.3 from fedora rawhide. IIRC
fedora template on ubuntu (with lxc-1.0.3) works just fine.


>
> 
>
> I have a doubt regarding binding a physical interface to a lxc-container.
>
> As per the instructions provided, we are creating a file at /run/netns
> say user1 and then attaching interfaces to the network namespace user1
> using ip command. Then we are using mount command to mount the network
> namespace user1 in the process.

No, what I wrote was:
- mount the container's net ns (so that you can modify it from the host)
- attach additional interfaces
- remove the netns (or unmount and delete, which would probably do the
same thing)

See how the order is different?

... and for the record, I'm not an lxc developer, so while the above
method might work, it's not necessarily the "correct" way to do so.

>
> If I restart the container then the container starts with the new
> process-id. Then if I try to mount the same network namespace user1 to
> new process I am not seeing the physical interfaces inside the
> container.
>
> Should I delete the network-namespace user1 when the container is
> stopped and create it again when we restart the container to make it
> work ?

err... don't use dynamically-attached interfaces?

if by "restart" you mean "shutdown and start again", then the way to
make it permanent is by editing the container's config file.

if by "restart" you mean "init 6 or reboot inside the container", then
yes, the newly-assigned net device will be back to the host, and no, I
don't know how to make it survive an "init 6".

-- 
Fajar
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] cpio: cap_set_file

[Stephan Sachse]

on Sun, Jun 8, 2014 at 1:25 AM, István Király  wrote:

> Hello list, ..
>
>
> I have tried your suggestion. Since LXC is built from source, the common's 
> file is at /usr/local/share/lxc/config. I rebooted the container after 
> commenting out that line, but still no go.
>
>
read this

https://www.redhat.com/archives/libvir-list/2014-February/msg01545.html

https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-February/008223.html


/me

-- 
Software is like sex, it's better when it's free!
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Networking in LXC

[Ajith Adapa]

Thanks for the reply @Fajar.

(From Host)
# lxc-attach -n root -- echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin

(Inside container)
# ifconfig
-bash: ifconfig: command not found
# echo $PATH
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin

As you mentioned there is a difference in PATH. I am using default
config to create a lxc container. Is it an issue with fedora or we
have to manually set it everytime a container is created ?



I have a doubt regarding binding a physical interface to a lxc-container.

As per the instructions provided, we are creating a file at /run/netns
say user1 and then attaching interfaces to the network namespace user1
using ip command. Then we are using mount command to mount the network
namespace user1 in the process.

If I restart the container then the container starts with the new
process-id. Then if I try to mount the same network namespace user1 to
new process I am not seeing the physical interfaces inside the
container.

Should I delete the network-namespace user1 when the container is
stopped and create it again when we restart the container to make it
work ?

Regards,
Ajith



On Tue, Jun 10, 2014 at 2:48 PM, Fajar A. Nugraha  wrote:
> On Tue, Jun 10, 2014 at 3:12 PM, Ajith Adapa  wrote:
>> Hi,
>>
>> First I need to really thank the community for helping me out in
>> starting LXC container on fedora 20.
>>
>> I have some basic questions regarding networking in LXC.
>>
>> 1. Is there any tutorial or doc regarding support for various network
>> options in lxc container ?
>
> Probably 
> http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html
> ?
>
> IIRC Fedora rawhide has lxc 1.0.3, so if you update to that you should
> have the same manpage. Otherwise you'd still be using lxc-0.9.0 which
> might be missing some features.
>
>>
>> 2. When I login into container and try ifconfig command I am getting
>> error saying "command not found" but I am able to run the same command
>> using lxc-attach. Any reason why ?
>>
>
> incorrect PATH? Try
>
> (from the host) lxc-attach -n CONTAINER_NAME -- echo $PATH
> (inside the container) echo $PATH
>
> in your case those two should display different output
>
>> 3. Is it possible to attach a physical interface to lxc container
>> which is in running state ? Currently we need to set the configuration
>> in the config file and restart the container.
>
> There's probably an easier way. The long way would be like this:
>
> # lxc-start -d -n template
>
> # lxc-info -n template
> Name:   template
> State:  RUNNING
> PID:8320  <= this is what we need, the PID of a process
> inside the container
> CPU use:0.93 seconds
> BlkIO use:  6.28 MiB
> Memory use: 18.72 MiB
> KMem use:   0 bytes
> Link:   vethDUGP01
>  TX bytes:  1.24 KiB
>  RX bytes:  84 bytes
>  Total bytes:   1.32 KiB
>
> # mkdir -p /run/netns
>
> # touch /run/netns/8320 <= this one could be any name you want, which
> would then be used by "ip ... netns"
>
> # mount --bind /proc/8320/ns/net /run/netns/8320
>
> # ip link show dummy1
> 8: dummy1:  mtu 1500 qdisc noqueue state DOWN mode
> DEFAULT group default
> link/ether 76:c6:a2:7f:c6:57 brd ff:ff:ff:ff:ff:ff
>
> # ip link set dummy1 netns 8320
>
> # ip link show dummy1
> Device "dummy1" does not exist.
>
> # lxc-attach -n template -- ip link show dummy1
> 8: dummy1:  mtu 1500 qdisc noop state DOWN mode
> DEFAULT group default
> link/ether 76:c6:a2:7f:c6:57 brd ff:ff:ff:ff:ff:ff
>
>
> --
> Fajar
>
>>
>> Regards,
>> Ajith
>> ___
>> lxc-users mailing list
>> lxc-users@lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Networking in LXC

[Fajar A. Nugraha]

On Tue, Jun 10, 2014 at 4:18 PM, Fajar A. Nugraha  wrote:
> On Tue, Jun 10, 2014 at 3:12 PM, Ajith Adapa  wrote:
>> Hi,
>>
>> First I need to really thank the community for helping me out in
>> starting LXC container on fedora 20.
>>
>> I have some basic questions regarding networking in LXC.
>>
>> 1. Is there any tutorial or doc regarding support for various network
>> options in lxc container ?
>
> Probably 
> http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html
> ?
>
> IIRC Fedora rawhide has lxc 1.0.3, so if you update to that you should
> have the same manpage. Otherwise you'd still be using lxc-0.9.0 which
> might be missing some features.
>
>>
>> 2. When I login into container and try ifconfig command I am getting
>> error saying "command not found" but I am able to run the same command
>> using lxc-attach. Any reason why ?
>>
>
> incorrect PATH? Try
>
> (from the host) lxc-attach -n CONTAINER_NAME -- echo $PATH
> (inside the container) echo $PATH
>
> in your case those two should display different output
>
>> 3. Is it possible to attach a physical interface to lxc container
>> which is in running state ? Currently we need to set the configuration
>> in the config file and restart the container.
>
> There's probably an easier way. The long way would be like this:
>
> # lxc-start -d -n template
>
> # lxc-info -n template
> Name:   template
> State:  RUNNING
> PID:8320  <= this is what we need, the PID of a process
> inside the container
> CPU use:0.93 seconds
> BlkIO use:  6.28 MiB
> Memory use: 18.72 MiB
> KMem use:   0 bytes
> Link:   vethDUGP01
>  TX bytes:  1.24 KiB
>  RX bytes:  84 bytes
>  Total bytes:   1.32 KiB
>
> # mkdir -p /run/netns
>
> # touch /run/netns/8320 <= this one could be any name you want, which
> would then be used by "ip ... netns"
>
> # mount --bind /proc/8320/ns/net /run/netns/8320
>
> # ip link show dummy1
> 8: dummy1:  mtu 1500 qdisc noqueue state DOWN mode
> DEFAULT group default
> link/ether 76:c6:a2:7f:c6:57 brd ff:ff:ff:ff:ff:ff
>
> # ip link set dummy1 netns 8320
>
> # ip link show dummy1
> Device "dummy1" does not exist.
>
> # lxc-attach -n template -- ip link show dummy1
> 8: dummy1:  mtu 1500 qdisc noop state DOWN mode
> DEFAULT group default
> link/ether 76:c6:a2:7f:c6:57 brd ff:ff:ff:ff:ff:ff
>



... and if you use real network device (e.g. eth1) instead of dummy1
like in my example, you should probably run this as well

# ip netns del 8320 (or whatever the netns name you choose above)

This is needed if you want the interface to be available again in the
host after the container shuts down. Otherwise, even when the
container is shutdown, the network namespace will still remains,
keeping the moved interface in it.

-- 
Fajar
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Networking in LXC

[Fajar A. Nugraha]

On Tue, Jun 10, 2014 at 3:12 PM, Ajith Adapa  wrote:
> Hi,
>
> First I need to really thank the community for helping me out in
> starting LXC container on fedora 20.
>
> I have some basic questions regarding networking in LXC.
>
> 1. Is there any tutorial or doc regarding support for various network
> options in lxc container ?

Probably 
http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html
?

IIRC Fedora rawhide has lxc 1.0.3, so if you update to that you should
have the same manpage. Otherwise you'd still be using lxc-0.9.0 which
might be missing some features.

>
> 2. When I login into container and try ifconfig command I am getting
> error saying "command not found" but I am able to run the same command
> using lxc-attach. Any reason why ?
>

incorrect PATH? Try

(from the host) lxc-attach -n CONTAINER_NAME -- echo $PATH
(inside the container) echo $PATH

in your case those two should display different output

> 3. Is it possible to attach a physical interface to lxc container
> which is in running state ? Currently we need to set the configuration
> in the config file and restart the container.

There's probably an easier way. The long way would be like this:

# lxc-start -d -n template

# lxc-info -n template
Name:   template
State:  RUNNING
PID:8320  <= this is what we need, the PID of a process
inside the container
CPU use:0.93 seconds
BlkIO use:  6.28 MiB
Memory use: 18.72 MiB
KMem use:   0 bytes
Link:   vethDUGP01
 TX bytes:  1.24 KiB
 RX bytes:  84 bytes
 Total bytes:   1.32 KiB

# mkdir -p /run/netns

# touch /run/netns/8320 <= this one could be any name you want, which
would then be used by "ip ... netns"

# mount --bind /proc/8320/ns/net /run/netns/8320

# ip link show dummy1
8: dummy1:  mtu 1500 qdisc noqueue state DOWN mode
DEFAULT group default
link/ether 76:c6:a2:7f:c6:57 brd ff:ff:ff:ff:ff:ff

# ip link set dummy1 netns 8320

# ip link show dummy1
Device "dummy1" does not exist.

# lxc-attach -n template -- ip link show dummy1
8: dummy1:  mtu 1500 qdisc noop state DOWN mode
DEFAULT group default
link/ether 76:c6:a2:7f:c6:57 brd ff:ff:ff:ff:ff:ff


-- 
Fajar

>
> Regards,
> Ajith
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] 1.0.3 on Debian 7.5 not consistent with documentation

[coolnodje]

Hi Nikola,

getting back to you about including lxc templates in the debian distrib:

It seems debian/control already contains your gist (exect maybe that the
"Replaces" and "Breaks" version are different: "lxc (<<
0.8.0~rc1-4ubuntu43)" but it'd probably not make any difference )

But still, it doesn't include the templates when building.

Everything seems ready to be compiled in lxc/templates but how do you
include it in the deb package creation?

configure.ac seems to include templates/Makefile so I guess it should be
built, i dont' get why not.

I could copy /usr/share/lxc/templates from an Ubuntu install, but I'd be
nice to know how to include it during build.

Sorry, I've never created a deb package and I'm not even too familiar
with builds under linux

Cheers

> Nikola Kotur 
> 22 May 2014 17:33
> On Wed, 21 May 2014 18:05:44 +0800
> coolnodje  wrote:
>
>> I realize there's no template coming with your Debian packaging
>> (/usr/share/lxc/templates is empty).
>> Was it intentional?
>
> Yes, I don't need templates, so I didn't add them to the package.
>
> In case you do want to build them, add this to debian/control:
>
> https://gist.github.com/kotnik/48ca8d5145854d096a83
>
>> I was also wondering why dpkg made me install dnsmasq-base (how does
>> it compare to dnsmasq?) but not dnsmasq, which is needed with for the
>> default /etc/default/lxc-net config.
>
> dnsmasq-base package contains the executable and documentation, dnsmasq
> is just the tooling needed to run it as a daemon.
>
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
> coolnodje 
> 16 May 2014 11:26
> apt-get remove lxc did the job before compiling 1.0.3.
>
> there's nothing left in /usr/bin and `which lxc-create` confirms it
> comes from /usr/local/bin
>
> So I understand, as expected, there shouldn't be any discrepancy
> between the Ubuntu 1.0.3 packaged version and the one I compiled on
> Debian, right?
>
> Something must have gone wrong then: could the option I used
> --with-distro=debian make a difference during ./configure?
>
> Also, I'd like to have everything in standard "packaged lxc" location
> except for the binaries. Would ./configure --prefix=/
> --bindir=/usr/local would do ?
> The INSTALL file in the distrib is really well done and useful but a
> confirmation would be helpful.
>
> Thanks
>
> coolnodje 
> 15 May 2014 18:34
> Hi,
>
> I've just compiled1.0.3 from source on Debian 7.5, without trouble.
>
> But I still get a behaviour that seem closer to v~0.8 that I got from
> apt-get beforehand, than to the version coming with Ubuntu 14.04.
>
> It's also not consistent with the https://linuxcontainers.org "How to
> use it?":
> no `lxc-ls --fancy` option, no --version available, no man page...
>
> Did I do something wrong when compiling ?
>
> ./configure --with-distro=debian
> make
> make install
> ldconfig
>
> cheers
> -nodje
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] Networking in LXC

[Ajith Adapa]

Hi,

First I need to really thank the community for helping me out in
starting LXC container on fedora 20.

I have some basic questions regarding networking in LXC.

1. Is there any tutorial or doc regarding support for various network
options in lxc container ?

2. When I login into container and try ifconfig command I am getting
error saying "command not found" but I am able to run the same command
using lxc-attach. Any reason why ?

3. Is it possible to attach a physical interface to lxc container
which is in running state ? Currently we need to set the configuration
in the config file and restart the container.

Regards,
Ajith
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users