-
Notifications
You must be signed in to change notification settings - Fork 536
Open
Labels
good first issueGood for newcomersGood for newcomers
Description
I have done the following
- I have searched the existing issues
- If possible, I've reproduced the issue using the 'main' branch of this project
Steps to reproduce
- Docker registry that has self signed cert
Current behavior
❯ container build -t test:test . --arch amd64
[+] Building 9.1s (4/13)
=> [resolver] fetching image...internal.cr/internal/base 0.0s
=> [internal] load .dockerignore 0.4s
=> => transferring context: 2B 0.4s
=> ERROR [linux/amd64 1/10] FROM internal.cr/internal/base:latest@sha256:cbc2d785b823ee730117c806ef73da8d6ce2aa774070e37221146041d66ee1bb 0.1s
=> => resolve internal.cr/internal/base:latest@sha256:cbc2d785b823ee730117c806ef73da8d6ce2aa774070e37221146041d66ee1bb 0.1s
=> CANCELED [internal] load build context 0.1s
=> => transferring context: 0.1s
------
> [linux/amd64 1/10] FROM internal.cr/internal/base:latest@sha256:cbc2d785b823ee730117c806ef73da8d6ce2aa774070e37221146041d66ee1bb:
------
Error: unknown (2): failed to solve: failed to load cache key: failed to do request: Head "https://internal.cr/v2/internal/base/manifests/sha256:cbc2d785b823ee730117c806ef73da8d6ce2aa774070e37221146041d66ee1bb": tls: failed to verify certificate: x509: certificate signed by unknown authority
Expected behavior
Use CA thats trusted by Keychain
Environment
- OS: 15.5 (24F74)
- Xcode: 15.5
- Container: container CLI version 0.2.0 (build: release, commit: 3b5c253)Relevant log output
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomers