[lxc-users] Howto ignore metadata.yaml template definitions ?
Hi, unfortunatelly the behaviour, to apply on certain actions specific template definitions to containers, ruines the stability of our containers. We do not want our network configuration other files being edited ( and ruined ) when we copy containers. Aswell as do not want the network configuration files to be (re)writen on the first start ( alias create ) of the containers. Is there any way to use the templates from images.linuxcontainers.org And ignore/remove/clean the metadata.yaml file ? Or can we tell lxc init, when we init a container, to ignore that ? Thank you ! -- Mit freundlichen Gruessen / Best regards Oliver Dzombic Layer7 Networks mailto:i...@layer7.net Anschrift: Layer7 Networks GmbH Zum Sonnenberg 1-3 63571 Gelnhausen HRB 96293 beim Amtsgericht Hanau Geschäftsführung: Oliver Dzombic ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] kernel messages appear in containers?
Hi all, I've noticed that some log messages that really belong to the host (like those from monthly RAID checks, for example) can appear in arbitrary containers instead - so they're spread all over the place. Is that normal/fixable? Cheers, Richard ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] kernel messages appear in containers?
On 2019-02-03 11:51, Richard Hector wrote: Hi all, I've noticed that some log messages that really belong to the host (like those from monthly RAID checks, for example) can appear in arbitrary containers instead - so they're spread all over the place. Is that normal/fixable? I'd say it's a "normal, bad default". You can fix it by adding this to your sysctl config file: kernel.dmesg_restrict = 1 Tomasz Chmielewski https://lxadm.com ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users