On Wed, Mar 23, 2016 at 10:41 AM, jjs - mainphrame wrote:
> Thanks for the feedback - Editing /etc/default/lxc-net in the ct solved the
> problem. That's one I won't forget.
... or remove lxc from inside the container. Are you using nested
containers? If no, there should be
Thanks for the feedback - Editing /etc/default/lxc-net in the ct solved the
problem. That's one I won't forget.
Regards,
Jake
On Tue, Mar 22, 2016 at 8:30 PM, Stéphane Graber
wrote:
> On Tue, Mar 22, 2016 at 08:08:53PM -0700, jjs - mainphrame wrote:
> > I'm starting to do
On Tue, Mar 22, 2016 at 08:08:53PM -0700, jjs - mainphrame wrote:
> I'm starting to do some testing with servers under lxd, and am confounded
> by the inability to configure networking as desired. Obviously I'm missing
> some elementary step here.
>
> For all my lxc servers, I could edit
I'm starting to do some testing with servers under lxd, and am confounded
by the inability to configure networking as desired. Obviously I'm missing
some elementary step here.
For all my lxc servers, I could edit /var/lib/lxc//config and
voila - full control over the network modes and devices per
oh ok, no problem.
So that could be something like
ps auxf|grep 19782|grep -v grep
165536 19782 0.0 0.4 37388 4464 ? Ss Mar15 0:05 \_ /sbin/init
stat /proc/19782
File: ‘/proc/19782’
Size: 0 Blocks: 0 IO Block: 1024 directory
Device: 4h/4d Inode: 47494006 Links: 9
Access:
D'oh, I was misremember how it works. And good thing too, as what I was
thinking couldn't possibly work. The number which should be used in
/proc/uptime is the st.st_ctime for /proc/.
Quoting Benoit GEORGELIN - Association Web4all (benoit.george...@web4all.fr):
> For container "ben"
>
> This
For container "ben"
This would be :
Dir: /sys/fs/cgroup/systemd/lxc/ben
File: tasks
/sys/fs/cgroup/systemd/lxc/ben] stat tasks
File: ‘tasks’
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 17h/23d Inode: 439 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 0/ root) Gid: (165536/
I cannot hide anything then !
You are right . I use openvswitch
cat /proc/1942/cgroup
10:blkio:/system.slice/lxd.service
9:memory:/system.slice/lxd.service
8:hugetlb:/system.slice/lxd.service
7:perf_event:/system.slice/lxd.service
6:cpuset:/system.slice/lxd.service
Quoting Benoit GEORGELIN - Association Web4all (benoit.george...@web4all.fr):
> Interesting, look the process monitor :
>
> root 1942 0.0 0.1 72544 1280 ? Ss Mar10 0:00 [lxc monitor]
> /var/lib/lxd/containers vps-01
> root 1984 0.0 0.0 72544 948 ? S Mar10 0:00 \_ [lxc monitor]
>
Interesting, look the process monitor :
root 1942 0.0 0.1 72544 1280 ? Ss Mar10 0:00 [lxc monitor]
/var/lib/lxd/containers vps-01
root 1984 0.0 0.0 72544 948 ? S Mar10 0:00 \_ [lxc monitor]
/var/lib/lxd/containers vps-01
root 19734 0.0 0.3 72544 3460 ? Ss Mar15 0:00 [lxc monitor]
On lun, mar 21, 2016 at 8:33 AM, slohani wrote:
Hello all,
I installed LXC on Ubuntu 14.04 using the following command:
sudo apt-get install lxc lxctl lxc-templates
But, lxc-top is not installed with this. How do I install lxc-top ?
which lxc version you have
2016-03-22 11:07 GMT-03:00 Tamas Papp :
>
>
> On 03/22/2016 02:51 PM, Fajar A. Nugraha wrote:
>
>> # echo "obase=16; 18446744073709551615"|bc
>>
>>
>
> Why is it in this so complicated format, whaah?
>
>
Its' base 10, the most used base in this planet (I'd
On 03/22/2016 02:51 PM, Fajar A. Nugraha wrote:
On Tue, Mar 22, 2016 at 8:44 PM, Fajar A. Nugraha wrote:
On Tue, Mar 22, 2016 at 7:55 PM, Tamas Papp wrote:
On 03/22/2016 01:51 PM, Dan Kegel wrote:
that is the largest possible value. convert it to
On Tue, Mar 22, 2016 at 8:44 PM, Fajar A. Nugraha wrote:
> On Tue, Mar 22, 2016 at 7:55 PM, Tamas Papp wrote:
>>
>>
>> On 03/22/2016 01:51 PM, Dan Kegel wrote:
>>>
>>>
>>> that is the largest possible value. convert it to base16 and you'll see.
>>>
>>
>> $
On Tue, Mar 22, 2016 at 7:55 PM, Tamas Papp wrote:
>
>
> On 03/22/2016 01:51 PM, Dan Kegel wrote:
>>
>>
>> that is the largest possible value. convert it to base16 and you'll see.
>>
>
> $ echo 18446744073709551615| base64
> MTg0NDY3NDQwNzM3MDk1NTE2MTUK
base16, not 64
>
>
On 03/22/2016 01:51 PM, Dan Kegel wrote:
that is the largest possible value. convert it to base16 and you'll see.
$ echo 18446744073709551615| base64
MTg0NDY3NDQwNzM3MDk1NTE2MTUK
What should I see here?
tamas
___
lxc-users mailing list
that is the largest possible value. convert it to base16 and you'll see.
On Mar 22, 2016 4:55 AM, "Tamas Papp" wrote:
> hi,
>
> $ lxc-cgroup -n bioreg-demo memory.limit_in_bytes
> 18446744073709551615
>
> And it has been never limited.
> I'm sure, it's a fake value. What
On 03/17/2016 07:20 PM, Serge Hallyn wrote:
Quoting Tamas Papp (tom...@martos.bme.hu):
On 03/17/2016 04:02 AM, Serge Hallyn wrote:
Quoting Tamas Papp (tom...@martos.bme.hu):
On 03/17/2016 12:09 AM, Serge Hallyn wrote:
Quoting Tamas Papp (tom...@martos.bme.hu):
hi,
I remember, that not
hi,
$ lxc-cgroup -n bioreg-demo memory.limit_in_bytes
18446744073709551615
And it has been never limited.
I'm sure, it's a fake value. What does it mean?
Linux v302 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Latest LXC 2.0.0.rc12.
10x
19 matches
Mail list logo