Ciao Michael,
simply the old-style /etc/init.d "start" that you show in your
post did not suffice.
I do note that you seem to have a mix of TCP ports here; both 80, 8080
(in the requested URL) and 8090 (in the podman invocation).
After your email, I double checked and I reported wrongly the port on
the browser url.. of course there were no others containers running a
the host
Anyway I tested the procedure using
* a vm as you did, and I confirm it is working... starting the services
using systemd simply works.
* a vm, stopping the services using the systemd and restarting them
using init.d and it works.
* docker running on a debian host, starting the services using init.d
and it works.
* podman running on a debian host, starting the services using init.d
and it works.
So case close... because the first try was running on a different
distribution, confining all the check to debian do not reproduce the issue.
Thanks for your feedback
Stefano
