Thanks for the pointers on VOLUME and STOPSIGNAL.
But please remove them from the examples as they’re not mandatory and that’s somewhat irritating. Or complement them with extensive comments to explain what you just did here.
Well at least that would be in conflict with your docs (link in last post). They say INITSYSTEM is deprecated. So either of these should be corrected, and I think it’s the example.
When you contact the example maintainer please also ask what CMD has to look like. I might have misunderstood this but the container terminates when it’s done with CMD. An initsystem replacement on the other hand should be a demon like systemd to run forever, shouldn’t it ?
I ended up issuing a CMD ‘sleep xxx’ so I can connect to the container (docker exec …) while that’s running but clearly that’s a hack, can you please provide a more clever example setup ?
Finally, my main issue and reason for playing around with the initsystem is still unresolved. Whenever I use
systemctl, I get error messages like those below. I read it’s a big hassle but is there a way to have systemd run as PID 1 ?
I think the most useful example would be the code one needs to deploy to get the initsystem working just the way it did before you introduced that breaking change.
Guess that’s most others would be interested, too.
systemctl status xyz
System has not been booted with systemd as init system (PID 1). Can't operate.