On Mi, 24.07.19 13:24, Jun Aruga (jar...@redhat.com) wrote:
> Sorry I posted my previous email wrongly.
>
> > > I have bunch of ideas, but all of them ugly (e.g., not own that file and
> > > create that directories in scriptlet). Do you
> > > have any ideas about this situation?
> >
> > Make
Sorry I posted my previous email wrongly.
> > I have bunch of ideas, but all of them ugly (e.g., not own that file and
> > create that directories in scriptlet). Do you
> > have any ideas about this situation?
>
> Make systemd create them? It has to manage them anyway.
I see this situation to
> I have bunch of ideas, but all of them ugly (e.g., not own that file and
> create that directories in scriptlet). Do you
> have any ideas about this situation?
Make systemd create them? It has to manage them anyway.
On Tue, Jul 23, 2019 at 5:30 PM Lennart Poettering wrote:
>
> On Di,
On Di, 23.07.19 10:56, Adam Jackson (a...@redhat.com) wrote:
> On Tue, 2019-07-23 at 11:01 +0200, Miroslav Suchý wrote:
> > Hi,
> > directories /proc/ and /sys/ are owned by filesystem package. This worked
> > in past where we needed those directories to
> > exist so we can mount the procfs and
On Tue, 2019-07-23 at 11:01 +0200, Miroslav Suchý wrote:
> Hi,
> directories /proc/ and /sys/ are owned by filesystem package. This worked in
> past where we needed those directories to
> exist so we can mount the procfs and sysfs.
>
> However this cause issues in containers:
>
Hi,
directories /proc/ and /sys/ are owned by filesystem package. This worked in
past where we needed those directories to
exist so we can mount the procfs and sysfs.
However this cause issues in containers:
https://bugzilla.redhat.com/show_bug.cgi?id=1548403
and during building where hacks are
