liquidmetal-dev / liquidmetal-dev/flintlock

Upgrade flintlock to use containerd v2

Open
#1,171 0 comments 0 reactions 1 assignee View on GitHub

@richardcase is already working on this.

Since Sep 3, 2026.

kind/feature
Dominant language
Go
Stars
1.5k
Forks
73
Avg merge
17h 24m
Merged PRs (30d)
30

Description

**Describe the solution you'd like:**
We are currently using containerd v1 internally in flintlock. We are running into issues configuring auth for private container registrys. Lets upgrade and use containerd v2 internally

**Why do you want this feature:**

So that we can take full advantage of containerd v2 features. We need to be able to pull images from private registries where the auth is configured in containerd config.

**Anything else you would like to add:**

Do we need to use `WithHostsDir` when pulling images

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.