fix container run

[NL-TCH]

this is extremly ugly, but the container exists when the script is ran, so after running the script we will tail /dev/null this will never stop so the container will never stop. again, super ugly, but i don't know a better way. maybe @jrcichra knows a cleaner method
fixes #18 resolves #18

[jrcichra]

There's also sleep infinity as an option.

[jrcichra]

You could switch the script back to a run.sh name and just include sleep infinity in there. Then you wouldn't need to shell out at the docker level.

[jrcichra]

I couldn't get either the docker-compose or the docker run method to work with the overriden CMD. I don't see systemd logs. We probably also need to run whatever the default for jrei/systemd-debian:12 is, or a crazy idea, include firewall-rules.sh as a systemd oneshot and leverage the fact that we're running systemd in a container.

[jrcichra]

The command is normally CMD ["/lib/systemd/systemd"] according to https://hub.docker.com/layers/jrei/systemd-debian/latest/images/sha256-1288ff231f93ba73984799d5881af10b50b1e4a4244bc9007560a1aa70d07fbf?context=explore

What works for me and is probably the easiest for right now is:

CMD [ "/bin/bash", "-c", "/home/firewall-rules.sh && /lib/systemd/systemd" ]

[billz]

What works for me and is probably the easiest for right now is:

CMD [ "/bin/bash", "-c", "/home/firewall-rules.sh && /lib/systemd/systemd" ]

Also confirm the above works. This seems to be a generally accepted method in common use.

[NL-TCH]

thanks for helping on this one!
the new commit uses the generally used workaround.

[billz]

You betcha! Resolves #11