[BUG] [DEV] Incorrect pull registry

Open Beginner friendly
#75 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, html
Domain
devops

Research direction

Start in ci/template.html at the referenced line around 652 and inspect how the topmost docker pull command is assembled. Compare its displayed namespace with the ghcr registry prefix used elsewhere in the template. Done means the pull command shows the correct registry and namespace; no specific test is mentioned, so verify the rendered output.

Written by the indexing model from the issue text.

Description

no-issue-activity
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

The topmost docker pull box uses the namespace for ghcr, but thats not reflected with prepending the registry
https://github.com/linuxserver/docker-ci/blob/develop/ci/template.html#L652

Expected Behavior

No response

Steps To Reproduce

.

Environment
- OS:
- How docker service was installed:
Docker creation
.
Container logs
.
Dominant language
Python
Stars
8
Forks
6
No merged PRs in 30d

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.

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.