New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot manage services inside chroot #955
Comments
Possibly related to #954 |
After having a bit of a think about this and a (really) quick test, I think option
I have only tested for Core and the few services I checked (stunnel, webmin & shellinabox), actually seem to start ok within a chroot?! However, this does appear to work:
However, there isn't any networking by default, so obviously more work is needed. I have done some very quick and dirty testing and here's the results:
So networking appears to work ok (once a proper resolv.conf has been created)?! |
That's exactly what they write in the referenced article. The nspawn shares networking with the host but cannot make any changes. There is a command-line argument to create a network namespace. But then you would have to create a /etc/network/interfaces entry for the host0 interface. And I think I also had to run dnsmasq on the host to serve DHCP. |
Added service wrapper in /usr/local/bin/service as a workaround to turnkeylinux/tracker/issues/955
We've discovered that this mainly affects Apache so far. We've added a We just need to make sure that we clean that up afterwards, definitely prior to release! |
We still need to finalise this and clean up afterwards, I'll assign myself for now... |
I'm closing this issue. Whilst it still remains as something of an issue, we've worked around it ok for now. We'll need to figure out something better at some point in the future, but hopefully by the time we're getting close to a release based on Debian buster, we'll have TKLX up and running and won't need to worry about this so much... |
Added service wrapper in /usr/local/bin/service as a workaround to turnkeylinux/tracker/issues/955
In SystemD services do not inherit the environment underwhich they were called unlike sysvinit. This means starting/stopping services within a chroot will fail.
Possible Solutions:
The text was updated successfully, but these errors were encountered: