[lxc-users] Container cannot write to /var/run
Bostjan Skufca
bostjan at a2o.si
Sat Apr 4 23:29:55 UTC 2015
Is systemd now supported as LXC guest's init system?
Anyhow, I would guess systemd creates ramdisk for /run (and /var/run)
which, by some funky interaction ends up non-writeable. I had (somewhat)
similar systemd issue on another project recently, where systemd created
/dev/log socket preemptively, and if syslog was not running, socket started
blocking syslog() syscalls. I might be wrong, but it might be systemd doing
something in an unconventional way which is causing trouble (unconventional
!= bad).
b.
On 4 April 2015 at 23:31, CDR <venefax at gmail.com> wrote:
> My Fedora 20 container, on a Ubuntu 14.04 server, cannot write to
> /var/run. Is there a secret reason that I use to fix it?
> Other containers with non-systemd OSs can write just fine to /var/run.
>
> Philip
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20150405/5bfb6fe0/attachment.html>
More information about the lxc-users
mailing list