Skip to content
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

Switch to using Podman to run the service #229

Open
cooper667 opened this issue Apr 1, 2022 · 0 comments
Open

Switch to using Podman to run the service #229

cooper667 opened this issue Apr 1, 2022 · 0 comments
Assignees
Labels
enhancement [Improvement] Enhancement request.

Comments

@cooper667
Copy link
Contributor

cooper667 commented Apr 1, 2022

Currently we use a very basic docker-compose file to run the service on the VM, but this occasionally doesn't restart correctly (we should ALSO work out why it's failing) and isn't really the correct way to run a persistent container on CoreOS.

A better approach would be using Podman in conjunction with SystemD, similar to the way described here:

https://www.tutorialworks.com/podman-systemd/

(that doesn't factor in how we update the container, ours are tagged with the commit hash.)

We could do something like, write the latest hash to a file somewhere and just have the SystemD or podman config read the tag from there? Then a deploy is:

  • Write new tag to that file
  • Restart the service
@cooper667 cooper667 added the enhancement [Improvement] Enhancement request. label Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement [Improvement] Enhancement request.
Projects
None yet
Development

No branches or pull requests

2 participants