Registry Mirror Support

Open
#339 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
docker, rust

Research direction

Start by reading the image pull flow and its registry configuration entry points; the issue does not name files or tests. Agree on how mirrors should be configured and selected before implementation. Done means Kiri can pull an image through a configured registry mirror; the issue does not define the configuration or expected behavior.

Written by the indexing model from the issue text.

Description

enhancement
What you're trying to do

Pull the image due to the network issue. Need a Registry Mirror Support

What you'd like Kiri to do

Let Kiri pull the image from the Registry Mirror.

Would you like to build it?

Yes, once we've agreed on the approach

Dominant language
Rust
Stars
7.5k
Forks
329
Avg merge
7h 48m
Merged PRs (30d)
105

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from libracoder/kiri

All issues in libracoder/kiri

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.