Re: [lxc-users] logging for applications in container

[Stepan Santalov]

On 02/16/2018 08:38 PM, Tomasz Chmielewski wrote:
> On 2018-02-17 02:20, Stepan Santalov wrote:
>> Hello!
>>
>> Is there a way to log to host's machine syslog by applications,
>> running in containers?
>> I've googled but with no luck.
> 
> rsyslog over TCP/UDP?

It looks obvious in case all the applications support it.
But they doesn't.

> 
> 
> Tomasz Chmielewski
> https://lxadm.com

-- 
Stepan Santalov
https://postgrespro.ru
+7 495 150 0691 # 23
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] logging for applications in container

[Tomasz Chmielewski]

On 2018-02-17 02:20, Stepan Santalov wrote:

Hello!

Is there a way to log to host's machine syslog by applications,
running in containers?
I've googled but with no luck.


rsyslog over TCP/UDP?


Tomasz Chmielewski
https://lxadm.com
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] logging for applications in container

[Stepan Santalov]

Hello!

Is there a way to log to host's machine syslog by applications, running in 
containers?
I've googled but with no luck.

-- 
Stepan Santalov
https://postgrespro.ru
+7 495 150 0691 # 23
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Migrating a rootfs back-and-forth lxc 2.0 <=> 3.0

[mslatter]

--This is an automated reply.--

The person to whom to your email was addressed is no longer with MAXIMUM 
Communications INC.

Unfortunately, due to spam control, we do NOT monitor this email address and 
have not received your request.
If you do intend to send an email to MAXIMUM Communications INC or are a 
customer of MAXIMUM Communications INC , 
please initiate an email addressed to Service at maximumcallcenter.com.

Thank you very much,

MAXIMUM Communications INC


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

Re: [lxc-users] Migrating a rootfs back-and-forth lxc 2.0 <=> 3.0

[Christian Brauner]

> Date: Thu, 15 Feb 2018 13:05:44 -0500 (EST)
> From: Adrian Pepper 
> To: lxc-users@lists.linuxcontainers.org
> Subject: [lxc-users] Migrating a rootfs back-and-forth lxc 2.0 <=> 3.0
> 
> Should one expect to encounter subtle (or perhaps not-so-subtle)
> problems if one takes the rootfs of a simple container created under
> one major version of lxc and uses it to replace the rootfs of a
> container previously created under another major version?
> (Replacing while the target is stopped, and then starting
> the container after the replacement).

No, that shouldn' cause any problems.

> 
> Assume that due diligence was done to keep the hostname in the
> filesystem was consistent with lxc.uts.name (or its equivalent
> in the relevant version), etc.
> 
> Or should one expect this to work seamlessly?  (The question would be
> whether there are hooks of some sort under the rootfs which might get
> automatically migrated in one direction (presumably "forwards" to a
> higher version), but not in the other direction, or possibly not in
> either direction at all).
> 
> Somewhat similarly, but conversely, I would assume that there is never
> any situation where having the same rootfs used simultaneously by more
> than one executing container would not be disastrous.  (in my case just
> a foreseeable possible accident, not something I have visions of exploiting).

That is a bad idea yes. For example, with system container you'd have
two init system thinking that they are in control of the whole rootfs
and fstree.

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