deckhouse / deckhouse/deckhouse-cli
d8 mirror push insecure ignored
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 7
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 33
Description
d8 mirror push images\ee nexus.local.lan:8083/dkp --registry-login user --registry-password password --insecure
Jan 2 11:49:57.235 INFO d8 version: v0.25.2
Jan 2 11:49:57.235 INFO Validating registry access
Jan 2 11:49:59.428 INFO ╔ Push Deckhouse platform
Jan 2 11:49:59.428 INFO ║ Unpacking platform package
Jan 2 11:52:12.537 INFO ║ Validating platform package
Jan 2 12:03:06.050 INFO ║ Pushing nexus.local.lan:8083/dkp
Jan 2 12:03:06.071 INFO ║ [1 / 704] Pushing image nexus.local.lan:8083/dkp:alpha
Jan 2 12:03:16.559 ERROR Push Deckhouse platform failed error="Push platform package: Push Image: Run push task: "push": task failed to many times, last error: Write nexus.local.lan:8083/dkp:alpha to registry: failed to push image: Get "https://nexus.local.lan:8083/v2/\": http: server gave HTTP response to HTTPS client"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the d8 mirror push command and reproduce the supplied command against the HTTP registry, checking how --insecure is handled before the push. Trace the registry validation and image-push entry points; done means the command honors --insecure and no longer sends HTTPS to the shown HTTP endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100