>
> allow-hotplug ens192
>
auto ens192
iface ens192 inet dhcp
auto eth0
iface eth0 inet manual
> pre-up ip link add link ens192 name eth0 type ipvlan mode l2
Then I add eth0 to my container is type=phys, and it works.
The weird thing is is that suppose I have a second "real" interface,
ens224,
ws but it makes sense from my viewpoint given my
> requirements.
>
> --
> Yannick Koehler
> --
> *From:* lxc-users on behalf
> of Andrey Repin
> *Sent:* June 15, 2020 10:51 AM
> *To:* Saint Michael ; All <
> lxc-users@lists.linuxcontainers.org
I have the same issue with plain LXC. Can somebody please post a container
config that would have the same rights as the host?
I actually move around my app in a container, the host is immaterial. It
used to work fine until I upgraded Ubuntu to 20.04, since then I get
permission denied on a fifo l
I have no idea what happens, but since I upgraded my Ubuntu to Focal,
lxc-start --version
4.0.2
Now my container gets a Acces Denied on a fifo object located in /tmp
I thought I gave the container all possible rights. What am I missing?
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.m
how long will it take, on average?
On Thu, Jun 4, 2020 at 6:10 PM Christian Brauner <
christian.brau...@ubuntu.com> wrote:
> On Thu, May 14, 2020 at 02:27:30PM -0400, Saint Michael wrote:
> > I use the ubuntu
> > add-apt-repository ppa:ubuntu-lxc/lxc-git-master
> > lx
Ubuntu 18.04
5.3.0-51-generic
lxc-start --version
4.0.0-devel
I can no longer start my containers, how do I get back to a version of LXC
that still works with this kernel?
lxc-start: opensips: tools/lxc_start.c: main: 314 Additional information
can be obtained by setting the --logfile and --logp
tu.com> wrote:
> On Thu, May 14, 2020 at 09:13:01AM -0400, Saint Michael wrote:
> > I am getting thousands of messages like this in my log, inside the
> > container:
> > May 14 13:09:38 iowa agetty[12473]: /dev/console: not a character device
> > May 14 13:09:48 iowa syst
I am getting thousands of messages like this in my log, inside the
container:
May 14 13:09:38 iowa agetty[12473]: /dev/console: not a character device
May 14 13:09:48 iowa systemd[1]: console-getty.service: Service hold-off
time over, scheduling restart.
May 14 13:09:48 iowa systemd[1]: console-get
lxc-download, or at least
> move to opt-in GPG, so this kind of issue should go away for everyone
> soon.
>
> On Sun, Apr 26, 2020 at 12:35 AM Saint Michael wrote:
> >
> > It does work, thanks. Is it possible to consider this a bug and add it
> to the next update?
> >
i, Apr 24, 2020 at 4:52 PM Saint Michael wrote:
> >
> > this works in an Ubuntu 18.04 host
> > lxc-create -t download -n u1 -- --dist ubuntu
> > but this does not
> > lxc-create -t download -n u1 -- --dist debian
> > Setting up the GPG keyring
> > ERROR:
this works in an Ubuntu 18.04 host
lxc-create -t download -n u1 -- --dist ubuntu
but this does not
lxc-create -t download -n u1 -- --dist debian
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver
lxc-create: u1: lxccontainer.c: create_run_template: 1626 Failed to create
contai
My host is Ubuntu 18.04 , and I am trying to do this:
lxc-create --template download --name debian10 -- --dist debian --release
buster --arch amd64
but it hangs on
Setting up the GPG keyring
I say the template as available in us.images.linuxcontainers.org
how do I connect that repository or downloa
d in step with Ubuntu LTS release. Choosing 20.04
> allows us to choose the latest ROS version, which in this case has
> advantages in terms of longevity of support and removal of Python 2
> dependencies.
>
> On Thu, Apr 23, 2020 at 1:52 PM Saint Michael wrote:
>
>> Is t
Is there any advantage on running 20.04 vs 18.04 with kernel 5.X?
On Thu, Apr 23, 2020 at 2:39 PM Mark Paterson wrote:
> Based on some success using LXC as a development environment on my
> desktop, we're looking at using LXC containers to deploy software to our
> robotics platform. The deployme
that
IP to static. My industry only uses public IPs.
On Wed, Mar 25, 2020 at 5:05 PM Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > It is a common practice to trust the DHCP server to keep track of free
> IPs
> > in a large network, like /21, and once the DHCP assi
Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > I use L2. Can somebody clarify what advantage/disadvantage is there for
> L2,L3,L3S?
> > I need also to be able to use DHCP inside the container. In a first boot
> I
> > get an IP from DHCP, and set the interf
2.168.88.1.
I tried to figure this scheme out with Netplan and I cannot see the light.
On Wed, Mar 25, 2020, 5:31 AM Fajar A. Nugraha wrote:
> On Tue, Mar 24, 2020 at 6:22 PM Saint Michael wrote:
> >
> > That scheme in my case would not work. I have two interfaces inside the
write to this list so apologies as I'm probably messing up
> the thread somehow.
>
> Saint Michael wrote: "... Vmware only allows multiple macs if the entire
> network is set in promiscuous mode..."
>
> Not strictly LXC/LXD related, but VMware has implemented two so
cuous mode, and
that kills performance. So basically the only workaround is ipvlan. As I
said, if you use type=phys and ipvlan inside the host, it works fine,
without altering the container.
On Tue, Mar 24, 2020 at 4:20 AM Fajar A. Nugraha wrote:
> On Mon, Mar 23, 2020 at 11:48 PM Saint M
Hi,
>
> just to make sure i understand right - you mean it is not supported in
> lxc-user-nic? And never was, so not a regression?
>
> Or has something regressed?
>
> On Mon, Mar 23, 2020 at 09:15:57AM -0400, Saint Michael wrote:
> > As I said, type=ipvlan does not work on the la
A. Nugraha wrote:
> On Fri, Mar 20, 2020 at 5:36 PM Saint Michael wrote:
> >
> > I use plain LXC, not LXD. is ipvlan supported?
>
> https://linuxcontainers.org/lxc/manpages//man5/lxc.container.conf.5.html
>
> --
> Fajar
> _
issue, but 99% of companies do the same. Very few people still use
physical boxes, we are all virtual.
On Fri, Mar 20, 2020 at 6:50 PM Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > I am using Ubuntu 18.04. In order to update to lxc 3.2.1 (since I need
> > ipvlan)
Yes, that is correct.
I installed LXC 3.2.1, and I am using now ipvlan, which allows the same MAC
to be used in a container as in the host. But I cannot ping anything.
Unless to use ipvlan I need to do something else.
My kernel is 5.30
On Fri, Mar 20, 2020 at 8:17 AM Tomasz Chmielewski wrote:
>
>
> I am using Ubuntu 18.04. In order to update to lxc 3.2.1 (since I need
>> ipvlan), I downloaded the tarball and compiled, installed, etc. Previously
>> I "apt remove --purge" every package with the word lcx in the name.
>
> But now lxc-ls shows nothing. what am I missing?
what is the right way
I use plain LXC, not LXD. is ipvlan supported?
Also my containers have public IPs, same network as the host. This is why I
cannot use NAT.
On Fri, Mar 20, 2020 at 12:02 AM Fajar A. Nugraha wrote:
> On Thu, Mar 19, 2020 at 12:02 AM Saint Michael wrote:
> >
> > The questio
As you probably know, the only way to have a Vmware VM with containers is
to enable promiscuous mode, that that kills the network performance and
causes high CPU usage for every other VM. So far the only way to
containerize under Vsphere is to add the max 10 interfaces allowed by
Vmware and assign
>
> The only thing that still works is phys, at least in Vmware virtual
> machines and the new kernel 5.0X
Any idea how can we make macvlan work again?
> Philip
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.
with kernel 5.3.0-29-generic, the only networking that works inside a
container is "phys". macvlan does not communicate and veth requires a
bridge, which I don't like.
Can somebody look into this:
Ubuntu 19.10
Philip Orleans
___
lxc-users mailing list
lx
Very important question.
On Fri, Dec 20, 2019 at 7:08 AM John Lane wrote:
> Hello,
>
> I have some lxc containers that I want to migrate to lxd. I'm using
> lxc/lxd v3 (3.1.8).
>
> I'm struggling to find documentation explaining how to configure the
> "phys" network type I use to assign a physic
AM Saint Michael wrote:
> >
> > Network Manager makes RHEL 8 and Centos 8 impossible to conteinarize.
> Please see that it detects a device type macvlan, when it should be really
> Ethernet. nmcli connection up Ethernet0 Error: Connection activation
> failed: No suitab
Network Manager makes RHEL 8 and Centos 8 impossible to conteinarize.
Please see that it detects a device type macvlan, when it should be really
Ethernet. nmcli connection up Ethernet0 Error: Connection activation
failed: No suitable device found for this connection (device lo not
available because
I use privileged containers for internal use. They ar supposed to have all
privileges, but when I did this
mount -o loop /CentOS-8-x86_64-1905-dvd1.iso /opt
mount: /opt: mount failed: Operation not permitted.
here is my configuration
lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0
lxc.mou
>
> I installed a Centos 8 container, but no matter what I do, the Network
> Mananager (nmcli) fails to find a suitable device for the connection. Can
> somebody show an example? It is possible that the networking may be broken
> inside a Centos 8 container. I copied a profile from a running Centos
Using thew repository, no services get created
On Sat, Nov 9, 2019, 6:44 AM Thomas Moschny
wrote:
> Am Fr., 1. Nov. 2019 um 17:26 Uhr schrieb Saint Michael >:
> >
> > In a regular Ubuntu 1804 we see this:
> > systemctl | grep -i lxc
> > var-lib-lxcfs.mount
AM Thomas Moschny
wrote:
> Am Sa., 26. Okt. 2019 um 17:05 Uhr schrieb Saint Michael <
> vene...@gmail.com>:
> >> As you all know, there is a new version of Centos, 8. I have not been
> able to install LXC on Centos 8. Does anyboyd have any idea how to do this
> from dn
7:05 Uhr schrieb Saint Michael <
> vene...@gmail.com>:
> >> As you all know, there is a new version of Centos, 8. I have not been
> able to install LXC on Centos 8. Does anyboyd have any idea how to do this
> from dnf or yum?
>
> LXC RPMs will eventually be available in EP
It did work fine, many thanks.
On Sun, Oct 27, 2019 at 9:44 AM Thomas Moschny
wrote:
> Am Sa., 26. Okt. 2019 um 17:05 Uhr schrieb Saint Michael <
> vene...@gmail.com>:
> >> As you all know, there is a new version of Centos, 8. I have not been
> able to install LXC o
>
> As you all know, there is a new version of Centos, 8. I have not been able
> to install LXC on Centos 8. Does anyboyd have any idea how to do this from
> dnf or yum?
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcont
8:18 PM Saint Michael wrote:
>
>> Thanks for the F grade.
>> In telecommunications, there is a special kind of software apps called
>> switches, which actually involve dozens of apps, scripts, etc. That kind of
>> complexity is only packageable in a container.
>>
>
Thanks for the F grade.
In telecommunications, there is a special kind of software apps called
switches, which actually involve dozens of apps, scripts, etc. That kind of
complexity is only packageable in a container.
Other industries can get away with far simpler infrastructures. A switch is
respo
I actually think that lxc.net.0.type = none is the solution to all my
problems. All I need to access my host is to use a different SSH port.
I didn't know this one. Thanks to all of you.
On Tue, May 28, 2019 at 1:47 AM Fajar A. Nugraha wrote:
> On Tue, May 28, 2019 at 12:39 PM Saint
SHD inside each container just fine.
On Mon, May 27, 2019 at 10:00 PM Fajar A. Nugraha wrote:
> On Mon, May 27, 2019 at 8:11 PM Saint Michael wrote:
>
>> I thought I did start the containers as privileged:
>>
>> lxc.include = /usr/share/lxc/config/ubuntu.common.conf
>> lxc
o
>
> >-Original Message-
> >From: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] On
> Behalf Of Saint Michael
> >Sent: Monday, May 27, 2019 1:49 PM
> >To: LXC users mailing-list
> >Subject: Re: [lxc-users] not allowed to change kernel parameter
8388608 unlimited bytes
On Mon, May 27, 2019 at 8:06 AM Kees Bos wrote:
> I probably missed it, but which release are you using on the host?
>
> And what's the output of
> prlimit -p 1
> ?
>
> On Mon, May 27, 2019, 1:52 PM Saint Michael wrote:
&g
My applications are very complex and involved many applications in the
traditional sense. It is a nightmare to install them.
My application runs on Centos but I prefer to use Ubuntu as LXC host.
I found that rsynching a container over the WAN is the only perfect way to
deploy.
The issue that kills
g with
> the host's).
>
> On Sat, May 25, 2019 at 09:36:25PM -0400, Saint Michael wrote:
> > some things do not work inside the container
> > sysctl -p
> > fs.aio-max-nr = 1048576
> > fs.aio-max-nr = 655360
> > fs.inotify.max_user_instances
directory
fs.file-max = 50
On Sat, May 25, 2019 at 9:28 PM Saint Michael wrote:
> Thanks
> Finally some help!
>
> On Sat, May 25, 2019 at 9:07 PM Stéphane Graber
> wrote:
>
>> On Sat, May 25, 2019 at 02:02:59PM -0400, Saint Michael wrote:
>> > Thanks to a
Thanks
Finally some help!
On Sat, May 25, 2019 at 9:07 PM Stéphane Graber wrote:
> On Sat, May 25, 2019 at 02:02:59PM -0400, Saint Michael wrote:
> > Thanks to all. I am sorry I touched a heated point. For me using
> > hard-virtualization for Linux apps is dementia. It should be
> Jake
>
> On Mon, May 20, 2019 at 9:25 AM Saint Michael wrote:
>
>> I am trying to use sysctl -p inside an LXC container and it says
>> read only file system
>> how do I give my container all possible rights?
>> Right now I have
>>
>>
host controls.
> Giving containers that is a bad idea.
>
> Sounds more to me like you want virtualization or bare metal app installs
> rather than containerization with LXC/LXD.
>
>
> Thomas
>
> On May 23, 2019, at 18:41, Saint Michael wrote:
>
> It means that the co
It means that the container has, or it must have all the power and rights.
It seems to be impossible to achieve that.
On Thu, May 23, 2019 at 6:35 PM Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > In my model, the host is unimportant, the container has the app, and I
> ha
In my model, the host is unimportant, the container has the app, and I have
only one container per host. That way I can migrate the apps from server to
server in a few minutes.
On Wed, May 22, 2019 at 6:50 PM Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > I am trying to u
I am trying to use sysctl -p inside an LXC container and it says
read only file system
how do I give my container all possible rights?
Right now I have
lxc.mount.auto = cgroup:mixed
lxc.tty.max = 10
lxc.pty.max = 1024
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
lxc.cg
master/templates/lxc-debian.in#L67
> for old debian system that still use sysvinit.
>
> --
> Fajar
>
> On Thu, Aug 9, 2018 at 9:18 AM, Saint Michael wrote:
>
>> The question is how can I use that for plan LXC.
>> I can install a box with LXD, bring the computer in,
The question is how can I use that for plan LXC.
I can install a box with LXD, bring the computer in, but then I want a
plain LXC container.
Is it doable?
On Wed, Aug 8, 2018 at 7:17 PM David Favor wrote:
> wrote:
> > Has anybody invented a procedure, a script, etc., to convert a running
> > m
Has anybody invented a procedure, a script, etc., to convert a running
machine to a LXC container? I was thinking to create a container of the
same OS, and then use rsync, excluding /proc /tmp/ /sys etc. Any ideas?
___
lxc-users mailing list
lxc-users@li
t;
> On Tue, Aug 7, 2018 at 8:18 PM +0200, "Serge E. Hallyn"
> wrote:
>
> Quoting Saint Michael (vene...@gmail.com):
>> > The default unprivileged 3.0 container does not allow fort the installation
>> > on MariaDB, so we are forced to make into a privileged
The default unprivileged 3.0 container does not allow fort the installation
on MariaDB, so we are forced to make into a privileged one. In my opinion
this involves a huge risk, since we need to install MySQL or Mariadb in
almost every conceivable container. LXC should allow to install at least
the
I solved the Autostart problem. But I want to use lxc 3.0.
On Tue, Jun 5, 2018 at 5:13 AM, Christian Brauner
wrote:
> On Mon, Jun 04, 2018 at 08:47:28PM -0400, Saint Michael wrote:
> > I am struggling with adding LXC 3.0 to the latest Fedora Server 27.
> > Also, in Fedora, the c
I am struggling with adding LXC 3.0 to the latest Fedora Server 27.
Also, in Fedora, the containers do no start automatically. I think I am
missing some step in the system configuration. Any idea how to add LXC 3.0
to Fedora and make lxc-autostart happen automatically?
_
Since the last yum update, all my Centos 7 containers on Ubuntu LTS hosts
have this issue when I use the command systemctl
Error getting authority: Error initializing authority: Could not connect:
Connection refused (g-io-error-quark, 39)
There is no information on the Internet about how to fix th
I cannot get the service incrond to work inside a container.
This service uses inotify to monitor the FS for changes.
My systctl.conf has plenty of watches, etc. That is not the issue
These are privileged containers.
Does anybody have any idea why this service does work on the host just fine
and n
Incrond is a service that monitors directories for file events and fires a
script.
It fails inside an LXC container.
Is there something I need to add to the configuration to make it work?
systemctl start incrond
Job for incrond.service failed because a timeout was exceeded. See
"systemctl status
I need to transfer a copy of a container that cannot be stopped. I don´t
mid if the data is slightly out of sync. Is there a way to do this? I tried
lxc-copy and it fails because the source is running.
___
lxc-users mailing list
lxc-users@lists.linuxconta
How do I get LXD 3.0 into regular ubuntu server 16.04.4 LTS (GNU/Linux
4.12.14-041214-generic x86_64)?
On Fri, Mar 30, 2018 at 8:53 PM, Sean McNamara wrote:
> On Fri, Mar 30, 2018 at 8:42 PM, Saint Michael wrote:
> > I am using LCX, plain vanilla. Is there a reading the can help m
I am using LCX, plain vanilla. Is there a reading the can help me move to
LXD 3.0? I am afraid I cannot see why would anybody use LXD vs regular LXC.
I can do anything I need, so far, with LXC. To copy a container to another
server I use rsync with some special parameters.
In general what is the gr
I want to use Fedora 27 as a container. Supposed I install a physical
machine with Fedora, how do I convert it to a container?
Somebody should create a script that would "containerize" any OS.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
Thanks for the solution. It works indeed.
Just out of curiosity, how did you find this out? I googled it far and wide
and there was nothing available.
On Sat, Nov 18, 2017 at 9:13 AM, Marat Khalili wrote:
> On 18/11/17 17:10, Saint Michael wrote:
>
> Yes, of course. It works bu
I don't control the server side. They upgraded to Secure FTP a few days ago.
On Mon, Nov 20, 2017 at 11:56 AM, Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > How do you rsync over SSH when all you have is a Plain Old FTP server to
> connect to?
> > Maybe th
On Sun, Nov 19, 2017 at 11:27 AM, Saint Michael wrote:
>
>> Last wee they upgraded to SFTP
>> It is one of those Federal Agencies that are behind in times.
>>
>>
>>
>>
>>
>>
>> On Sun, Nov 19, 2017 at 2:14 PM, Ron Kelley wrote:
>>
>
h is by far the slowest because of the
> ssh cipher. Rsync over nfs mount is very fast - almost as fast as a local
> copy.
> >
> > -Ron
> >
> >
> >
> >
> >
> >
> > > On Nov 18, 2017, at 9:37 PM, Saint Michael wrote:
> > >
> &
variety of network connections (rsync daemon, nfs, rsync via ssh). My
> experience has shown rsync over ssh is by far the slowest because of the
> ssh cipher. Rsync over nfs mount is very fast - almost as fast as a local
> copy.
>
> -Ron
>
>
>
>
>
>
> > On No
How do you rsync over SSH when all you have is a Plain Old FTP server to
connect to?
Maybe there is something I need to learn.
On Sat, Nov 18, 2017 at 5:08 PM, Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > I need to do an rsync of hundreds of files very morning. The lea
Let me try that
On Sat, Nov 18, 2017 at 9:13 AM, Marat Khalili wrote:
> On 18/11/17 17:10, Saint Michael wrote:
>
> Yes, of course. It works but only if autodev=0
> That is the issue.
>
>
> Even as:
>
> lxc.hook.autodev = sh -c 'mknod ${LXC
Yes, of course. It works but only if autodev=0
That is the issue.
On Sat, Nov 18, 2017 at 9:06 AM, Marat Khalili wrote:
> On 16/11/17 18:50, Saint Michael wrote:
>
> The issue is with fuse, that is why I keep
> lxc.autodev=0
> if I do not, if I set it to 1, then fuse does not
I need to do an rsync of hundreds of files very morning. The least complex
way to achieve that is to do an rsync with some parameters that narrow down
what files I need.
Is there a better way?
On Fri, Nov 17, 2017 at 11:43 PM, Andrey Repin wrote:
> Greetings, Saint Mich
developers list.
On Thu, Nov 16, 2017 at 10:45 AM, Fajar A. Nugraha wrote:
> On Thu, Nov 16, 2017 at 10:04 PM, Saint Michael wrote:
>
>> I missfired.
>> But I found the culprit, it is
>> lxc.autodev = 0
>>
>> if I use
>> lxc.autodev = 1
>> the issue
I missfired.
But I found the culprit, it is
lxc.autodev = 0
if I use
lxc.autodev = 1
the issue does not happens
Can somebodu shed any light on the ramifications of this?
Some additional information: I use fuse inside my containers.
Philip
On Thu, Nov 16, 2017 at 9:52 AM, Saint Michael wrote
THAT WORKED
But the new key is
lxc.tty.dir = lxc
On Thu, Nov 16, 2017 at 9:32 AM, Marat Khalili wrote:
> On 16/11/17 14:58, Saint Michael wrote:
>
> lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0
> lxc.mount.entry = sysfs sys sysfs defaults 0 0
> lxc.mount.entry = /cd
et. I
also did this inside the container
systemctl stop console-getty
systemctl disable console-getty
systemctl mask console-getty
remove /dev/tty0
systemctl stop getty@tty1.service; systemctl mask getty@tty1.service
but it keeps happening.
Philip
On Thu, Nov 16, 2017 at 6:58 AM, Saint Michael
lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0
lxc.mount.entry = sysfs sys sysfs defaults 0 0
lxc.mount.entry = /cdr cdr none bind 0 0
lxc.mount.auto = cgroup:mixed
lxc.tty = 10
lxc.pts = 1024
lxc.cgroup.devices.deny = a
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1
, since a container does hijack the host's TTY.
Any confirmation of this?
I cannot believe this is impossible to solve.
On Wed, Nov 15, 2017 at 10:19 PM, Fajar A. Nugraha wrote:
> On Thu, Nov 16, 2017 at 10:04 AM, Saint Michael wrote:
>
>> I did apply all suggested solutio
, 2017 at 9:42 PM, Andrey Repin wrote:
> Greetings, Saint Michael!
>
> > My host is Ubuntu LTS
>
> Which "LTS"?…
>
> > and my container is Centos 7.
>
> And what you are using for containers?
> LXC? LXD? Which version?
>
> > Every time the
My host is Ubuntu LTS and my container is Centos 7. Every time the server
boots, the container takes over the tty0 of the server, Ubuntu, and freezes
the interface. The only way to log to the server itsef is to press ALT+F2
and use the second tty. I tried to remobve tty0 on the gest, and also this
I add myself to the question.
On Wed, Sep 27, 2017 at 8:48 AM, Tomasz Chmielewski wrote:
> # lxc exec some-container /bin/bash
> The configuration file contains legacy configuration keys.
> Please update your configuration file!
>
>
>
> Is there a way to tell find out which ones are legacy witho
Exactly. Please include the script.
On Mon, Sep 25, 2017 at 9:44 PM, Sergiusz Pawlowicz wrote:
> Hi, I'm getting:
>
> The configuration file contains legacy configuration keys.
> Please update your configuration file!
>
> but I do not see the update script inside the ubuntu xenial package:
>
> #
Very important question
On Tue, Sep 19, 2017 at 9:18 PM, Ivan Kurnosov wrote:
> Hi,
>
> there is a server that currently runs ~100 containers.
>
> One of those containers is a subject of my interest.
>
> Brief details about the container: it runs ubuntu xenial, and it's a tiny
> file server (sam
I have a lot of memory management issues using pure LXC. In my case, my box
has only one container. I use LXC to be able to move my app around, not to
squeeze performance out of hardware. What happens is my database gets
killed the OOM manager, although there are gigabytes of RAM used for cache.
Th
The container is Debian 7. It does not use systemd.
On Thu, May 18, 2017 at 9:01 PM, Fajar A. Nugraha wrote:
> On Fri, May 19, 2017 at 7:45 AM, gunnar.wagner <
> gunnar.wag...@netcologne.de> wrote:
>
>> a bit OT related to this thread but from what Fajar has posted here it
>> almost sounds like
The host is Ubuntu 16.04.2 LTS, the container is Debian GNU/Linux 7
On Thu, May 18, 2017 at 8:13 PM, Saint Michael wrote:
> In my debian container, it is file.
> It gets recreated all the time I reboot.
> what am I doing wrong?
> This is the config file
> lxc.mount.entry = proc
= cgroup:mixed
lxc.cap.drop=
lxc.kmsg=0
lxc.utsname = dialer-20
On Thu, May 18, 2017 at 8:07 PM, Fajar A. Nugraha wrote:
> On Thu, May 18, 2017 at 11:06 PM, Saint Michael wrote:
>
>> On Ubuntu 16.04..2 LTS, kernel 4.4.0-78-generi
>>
>> inside a container I erase the fil
On Ubuntu 16.04..2 LTS, kernel 4.4.0-78-generi
inside a container I erase the file /etc/mtab
the containers start, a new file /etc/mtab gets created
I stop the container,
I start the container
the line with tmpfs starts growing ad -infinitum, this way
tmpfs /run/shm tmpfs
rw,noexec,nosuid,nodev,s
I use the new kernel 4.10 and you may do with XFS almost anything you can
do with BTRFS or ZFS, like duperemove, and it is still XFS.
On Fri, Apr 28, 2017 at 8:40 PM, Andrey Repin wrote:
> Greetings, Simos Xenitellis!
>
> > 2. The Linux kernel lacks ZFS support, thus requires to compile it by
>
My application could no use more space per thread on the temporary file
system. These are privileged containers and I need that they have access to
the full resources of the parent, which are essentially unlimited.
How can I make sure that the container has no constraints? My config now is
lxc.mo
On a brand new Fedora 25 system, how do you make sure that containers
marked for autostart, actually do start? They do not rihgt now. Is there
systemctl service that can do the job?
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lis
My device is a network interface.
Is there any code I may execute on the host to make sure the container
starts again if I need to stop it?
On Mon, Nov 14, 2016 at 10:50 AM, Stéphane Graber
wrote:
> On Mon, Nov 14, 2016 at 03:18:54AM -0500, Saint Michael wrote:
> > In LXC networking
In LXC networking type phys, the network interface correctly disappears
from the host, but the container never "returns" the device when it gets
stopped, and it never starts again, unless the host is rebooted, since the
device is not there.
I think the device should go back to the host so the conta
, but never reaching their destination.
So LXC networking mode macvilan is not working after the latest Ubuntu host
updates.
On Wed, Nov 9, 2016 at 9:56 AM, Saint Michael wrote:
> I SOLVED
> Many thanks to all. Using your input I concluded that the issue was not in
> LXC or the Kernel
I SOLVED
Many thanks to all. Using your input I concluded that the issue was not in
LXC or the Kernel. In fact. the colo changed the subnets without telling me.
Yours
Federico
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.
0
net.ipv4.conf.lo.rp_filter = 0
But the response from the container never reach the machine that is trying
to ping the container.
Any idea what can be wrong?
The fact is I did not change anything on my network.
On Wed, Nov 9, 2016 at 9:42 AM, Saint Michael wrote:
> I don't know how to do
1 - 100 of 148 matches
Mail list logo
