[lxc-users] Ipvlan Network weirdness

> > 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,

Re: [lxc-users] Running unprotected system container

t 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>

Re: [lxc-users] Running unprotected system container

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

[lxc-users] Upgrade to Ubuntu Focal kills LXC critica functionality

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

Re: [lxc-users] Issue withe latest version from git

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

[lxc-users] URGENT Panic when upgrading Kernel

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

Re: [lxc-users] Issue withe latest version from git

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 systemd[1]: co

[lxc-users] Issue withe latest version from git

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]:

Re: [lxc-users] lxc-create -t download

oad, 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? > > > >

Re: [lxc-users] lxc-create -t download

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:

[lxc-users] lxc-create -t download

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

[lxc-users] How to use https://us.images.linuxcontainers.org/

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

Re: [lxc-users] LXC for real-time robotics

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 there

Re: [lxc-users] LXC for real-time robotics

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

Re: [lxc-users] Networking

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

Re: [lxc-users] Networking

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 i

Re: [lxc-users] Networking

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

Re: [lxc-users] Networking

ite 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 soluti

Re: [lxc-users] Networking

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

Re: [lxc-users] Networking

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

Re: [lxc-users] Networking

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 > _

Re: [lxc-users] Updating to LXC 3.2.1 fails

an 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 > > ipv

Re: [lxc-users] Quick Question

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:

[lxc-users] Updating to LXC 3.2.1 fails

> > 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

Re: [lxc-users] Networking

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

[lxc-users] Networking

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

[lxc-users] macvlan for networking is dead

> > 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

[lxc-users] networking is broken

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

Re: [lxc-users] Converting network from LXC to LXD

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

Re: [lxc-users] Network Manager makes RHEL 8 and Centos 8 impossible to use as a container

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:

[lxc-users] Network Manager makes RHEL 8 and Centos 8 impossible to use as a container

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

[lxc-users] mounting an ISO insider a container

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-users] Centos 8 networking

> > 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

Re: [lxc-users] Impossible to instal LXC on Centos 8

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

Re: [lxc-users] Impossible to instal LXC on Centos 8

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 > fr

Re: [lxc-users] Impossible to instal LXC on Centos 8

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 EPEL8.

Re: [lxc-users] Impossible to instal LXC on Centos 8

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

[lxc-users] Impossible to instal LXC on Centos 8

> > 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

Re: [lxc-users] not allowed to change kernel parameters inside container

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. >> > &g

Re: [lxc-users] not allowed to change kernel parameters inside 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

Re: [lxc-users] not allowed to change kernel parameters inside container

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 Mich

Re: [lxc-users] not allowed to change kernel parameters inside container

nside 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.moun

Re: [lxc-users] not allowed to change kernel parameters inside container

; >-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 parameters inside &

Re: [lxc-users] not allowed to change kernel parameters inside container

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: > >> My applica

Re: [lxc-users] not allowed to change kernel parameters inside container

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

Re: [lxc-users] not allowed to change kernel parameters inside container

> > 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 = 8192 > > kernel.pty.m

Re: [lxc-users] not allowed to change kernel parameters inside container

or 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

Re: [lxc-users] not allowed to change kernel parameters inside container

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 shou

Re: [lxc-users] not allowed to change kernel parameters inside container

> 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 >> >>

Re: [lxc-users] not allowed to change kernel parameters inside container

rols. > 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 container

Re: [lxc-users] not allowed to change kernel parameters inside container

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

Re: [lxc-users] not allowed to change kernel parameters inside container

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

[lxc-users] not allowed to change kernel parameters inside container

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

Re: [lxc-users] Convert virtual machine to LXC container

s/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, but then I want a &

Re: [lxc-users] Convert virtual machine to LXC container

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 > >

[lxc-users] Convert virtual machine to LXC container

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

Re: [lxc-users] unprivileged containers and databases

> > 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 privileg

[lxc-users] unprivileged containers and databases

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

[lxc-users] Sudden error in ALL containers

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

[lxc-users] Incrond service fails inside a container

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

[lxc-users] Inotify does not work in a privileged container

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

[lxc-users] LXC Copying a running container

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

Re: [lxc-users] LXD project status

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 <smc...@gmail.com> wrote: > On Fri, Mar 30, 2018 at 8:42 PM, Saint Michael <vene...@gmail.com> wrote: > > I am usi

Re: [lxc-users] LXD project status

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

[lxc-users] how to crate a new Fedora LXC-template

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

Re: [lxc-users] TTY issue

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 <m...@rqc.ru> wrote: > On 18/11/17 17:10, Saint Michael wrote: > > Yes, of c

Re: [lxc-users] TTY issue

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 <anrdae...@yandex.ru> wrote: > Greetings, Saint Michael! > > > How do you rsync over SSH when all you have is a Plain Old FTP server to >

Re: [lxc-users] TTY issue

> > J > > On Sun, Nov 19, 2017 at 11:27 AM, Saint Michael <vene...@gmail.com> wrote: > >> Last wee they upgraded to SFTP >> It is one of those Federal Agencies that are behind in times. >> >> >> >> >> >> >> On Sun, Nov 1

Re: [lxc-users] TTY issue

; > > On Nov 19, 2017, at 10:17 AM, Saint Michael <vene...@gmail.com> wrote: > > > > The server is at a the government. I would go to jail. > > But thanks for the input. > > > > On Sun, Nov 19, 2017 at 8:03 AM, Ron Kelley <rkelley...@gmail.com> &g

Re: [lxc-users] TTY issue

ong time and using a > 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 > > > >

Re: [lxc-users] TTY issue

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 <anrdae...@yandex.ru> wrote: > Greetings, Saint Michael! > > > I need to do an rsync of hundreds of

Re: [lxc-users] TTY issue

Let me try that On Sat, Nov 18, 2017 at 9:13 AM, Marat Khalili <m...@rqc.ru> 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 ${LX

Re: [lxc-users] TTY issue

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 <m...@rqc.ru> 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

Re: [lxc-users] TTY issue

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 <anrdae...@yandex.ru> wrote: > Greetings, Sain

Re: [lxc-users] TTY issue

developers list. On Thu, Nov 16, 2017 at 10:45 AM, Fajar A. Nugraha <l...@fajar.net> wrote: > On Thu, Nov 16, 2017 at 10:04 PM, Saint Michael <vene...@gmail.com> wrote: > >> I missfired. >> But I found the culprit, it is >> lxc.autodev = 0 >> >&g

Re: [lxc-users] TTY 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 <v

Re: [lxc-users] TTY issue

THAT WORKED But the new key is lxc.tty.dir = lxc On Thu, Nov 16, 2017 at 9:32 AM, Marat Khalili <m...@rqc.ru> 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 > l

Re: [lxc-users] TTY issue

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 <v

Re: [lxc-users] TTY issue

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

Re: [lxc-users] TTY issue

, 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 <l...@fajar.net> wrote: > On Thu, Nov 16, 2017 at 10:04 AM, Saint Michael <vene...@gmail.com> wrote: >

Re: [lxc-users] TTY issue

, 2017 at 9:42 PM, Andrey Repin <anrdae...@yandex.ru> 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? > &g

[lxc-users] TTY issue

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

Re: [lxc-users] "The configuration file contains legacy configuration keys" - which ones?

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

Re: [lxc-users] LXC 2.1 to be released on Tuesday (call for testing)

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

Re: [lxc-users] How to properly find what consumes memory inside the container.

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

Re: [lxc-users] LXD 2.14 - Ubuntu 16.04 - kernel 4.4.0-57-generic - SWAP continuing to grow

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.

Re: [lxc-users] Possible bug

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 >>

Re: [lxc-users] Possible bug

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 <vene...@gmail.com> 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

Re: [lxc-users] Possible bug

= cgroup:mixed lxc.cap.drop= lxc.kmsg=0 lxc.utsname = dialer-20 On Thu, May 18, 2017 at 8:07 PM, Fajar A. Nugraha <l...@fajar.net> wrote: > On Thu, May 18, 2017 at 11:06 PM, Saint Michael <vene...@gmail.com> wrote: > >> On Ubuntu 16.04..2 LTS, kernel 4.4.0-78-generi >>

[lxc-users] Possible bug

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

Re: [lxc-users] Running LXD on those new ARM64 cloud servers by Scaleway

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

[lxc-users] Increase temp space /tmp

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-users] Fedora 25 fails to autostart LXC containers

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

Re: [lxc-users] LXC networking bug

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 <stgra...@ubuntu.com> wrote: > On Mon, Nov 14, 2016 at 03:18:54AM -0500, Saint Michael wrote: &

[lxc-users] LXC networking bug

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

Re: [lxc-users] Networking issue

, 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 <vene...@gmail.com> wrote: > I SOLVED > Many thanks to all. Using your input I concluded that the issue was

Re: [lxc-users] Networking issue

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

Re: [lxc-users] Networking issue

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 <vene...@gmail.com> wrote: &g

Re: [lxc-users] Networking issue

our guess, as the other feedback you got > also points to the kernel. If that solves it, go file a kernel bug. > > 2016-11-09 7:33 GMT+01:00 Saint Michael <vene...@gmail.com>: > >> It was working fine until a week ago. >> I have two sites, it happened on both, so the issue is

Re: [lxc-users] How to open a ticket with LXC

one. > > I understand that as a user you don't really want to have to care about > who's providing what software, but everyone will be able to do their jobs > much better if they can focus on what they focus on. > > -serge > > Quoting Saint Michael (vene...@gmail.com): >

  1   2   >