I just want to share this, after unsuccessfully trying to understand the reason looking at the docs about nesting.
I searched the web for a common application problem, like "/run/php directory not created by php-fpm service". Lots of answers but found none focusing the real problem.
In my case, I was running a privileged container with long uptimes, so I can't remember in detail if that happened before and the solution (i.e. manually creating the directory). I got close when checked the service:
Trying to start it manually threw a CREDENTIALS error. I found that in another server i had a similar container without this problem. I thought about the "magic of nesting", and found that the working container had nesting enabled. So, I enabled the nesting feature, rebooted the container and everything started to work as expected.
I hope this helps someone from spending a lot of time searching for "magic" when there's no apparent reason for something not working.
Regards.
I searched the web for a common application problem, like "/run/php directory not created by php-fpm service". Lots of answers but found none focusing the real problem.
In my case, I was running a privileged container with long uptimes, so I can't remember in detail if that happened before and the solution (i.e. manually creating the directory). I got close when checked the service:
Code:
systemctl status systemd-tmpfiles-setupTrying to start it manually threw a CREDENTIALS error. I found that in another server i had a similar container without this problem. I thought about the "magic of nesting", and found that the working container had nesting enabled. So, I enabled the nesting feature, rebooted the container and everything started to work as expected.
I hope this helps someone from spending a lot of time searching for "magic" when there's no apparent reason for something not working.
Regards.