Add check to CI pipeline that docker container can start

[peterchave]

The CI pipeline is building valid containers, but when the container is launched it errors with shared library failure.

# docker run --rm ghcr.io/openmoq/o-rly:3ac31ea
/usr/local/bin/o-rly: error while loading shared libraries: libsodium.so.23: cannot open shared object file: No such file or directory

Can we add a step the CI pipeline to test launch the produced container and verify it doesn't throw any errors out of the box? Further down the road we can add more of the conformance checks, but at least for now can we add a basic sanity check?

[peterchave]

Put up a suggestion for a quick smoke test on the docker image here:
https://github.com/openmoq/o-rly/blob/ci-smoke-test/.github/workflows/ci-main.yml

[gmarzot]

#57

Suggest closing this issue based in the smoke test (minor execute and hit health api endpoint) and create another issue for autmated deployment with certs. need definition of consistent deployment testbed (i see you have one !). The linode ci runner also another viable single node deployment target for more involved test (small fire not just smoke?)

[peterchave]

Agree - smoke test added, docker image now working!