Zobelisk GitHub Actions container frequently goes down

[cbrxyz]

What needs to change?

The GitHub Actions Docker container running our CI builds repeatedly goes down on Zobelisk, requiring someone to provide a new authentication key every time it needs to be restarted. It would be great if the container could be more reliable, or at least if it was easier to re-launch the existing container.

How would this task be tested?

1. This one is a little hard to test, since it usually takes a while for the GitHub Actions container to go down. Maybe you could make the container forcefully shut down after a shorter amount of time, and then ensure that the container comes alive again.

Contacts

• We need help from the mechanical team.
• We need help from the electrical team.
• We need help from Dr. Schwartz or other faculty.
• We need help from a company or an organization.
• We need help from another UF staff member or organization (ex, facilities).

[lynettehemingway]

Update: I am learning about strategies to improve the reliability of the GitHub Actions Docker container, including exploring automated key management solutions, understanding how to implement health checks and auto-restart mechanisms, and researching best practices for testing and stress-testing containers for best performance.