Menu

Docker x509 certificate signed by unknown authority in CI
📰

Docker x509 certificate signed by unknown authority in CI

DEV Community: docker·Kay·about 22 hours ago
#Hzrpp4I3
#devtodocker#devto#dev#registry#certificate
Reading 0:00
15s threshold

Docker x509 certificate signed by unknown authority in GitHub Actions means the daemon reached your registry, read the certificate it presented, and found no trusted root behind it, so to fix registry TLS you install that CA where Docker looks for it. Marking the registry insecure also silences the error, and it turns off the check that was protecting every layer the job pulls.

Three places hold a CA, and they serve different clients. Installing one and testing with another is why this error survives the first fix.

What this error means

Public images pull normally and one host fails, every time, at the first request rather than part way through a download. Two wordings are in circulation: the older one ends the Get line with "x509: certificate signed by unknown authority", and newer clients put "tls: failed to verify certificate" in front of it, which is the shape cnoe-io/idpbuilder#520 reports.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.