buildkitd registry-auth-tlscontext flag not support
Open
Nobody has claimed this yet.
kind/enhancement
status/triage
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
Description
Add registry-auth-tlscontext flag to support push image to insecurity registry.
When I use harbor as my private registry. I can not push image to harbor, because
ERROR: failed to solve: failed to push harbor.xxxx.com/tenant1-project1-docker/example-backend:202404031157: failed to authorize: failed to fetch oauth token: Post "https://harbor.xxxx.com/service/token": tls: failed to verify certificate: x509: certificate signed by unknown authority
When buildkit fetch token for auth, it use https.
Contributor guide
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
The issue names buildkitd's registry-auth-tlscontext flag and the Harbor token-fetch path, but no files or tests. Start by locating the registry authentication and HTTPS token-fetch code, then trace how buildkitd handles registry TLS settings. Done means the flag is documented and a push to a registry with an untrusted certificate can authenticate successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100