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

Handle existing containerd instances automatically on Github Actions #30

Open
jnsgruk opened this issue Jan 28, 2025 · 1 comment
Open

Comments

@jnsgruk
Copy link
Owner

jnsgruk commented Jan 28, 2025

In a recent commit, I made the move to remove Docker, Containerd, etc. from the Github Actions runner before running the tests. This is because with these packages present, the k8s snap fails to bootstrap since it detects the presence of the /run/containerd directory.

I looked at specifying a bootstrap config file per the K8s snap docs, but simply specifying a single option then interferes with the rest of the bootstrap configuration - perhaps there is a way to use the default configuration and only specify the containerd-base-dir that I missed?

In any case, one possible solution would be to detect when concierge is running on a Github Actions runner and simply disable the containerd service and delete the socket in /run as a non-destructive measure.

@jnsgruk
Copy link
Owner Author

jnsgruk commented Jan 30, 2025

The K8s team are looking into providing a command-line option that will dump the default bootstrap configuration.

Once this is in place, I think the right route to solve this problem is to:

  • Dump the default bootstrap config
  • Modify the containerd-base-dir
  • Bootstrap with the newly modified file

This should result in fairly minimal code changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant