Skip to content

DOCKER_CONTENT_TRUST_SERVER not working correctly with port number #1949

Description

@peterthomassen

Description

DOCKER_CONTENT_TRUST_SERVER does not work correctly if a port number is provided.

Steps to reproduce the issue:

  1. export DOCKER_CONTENT_TRUST=1
  2. export DOCKER_CONTENT_TRUST_SERVER=https://notary.docker.io:443
  3. docker image pull mariadb/server

Describe the results you received:

Using default tag: latest
unable to reach trust server at this time: 503.

This appears to be a HTTP 503 error.

Describe the results you expected:

Using default tag: latest
Error: remote trust data does not exist for docker.io/mariadb/server: notary.docker.io:443 does not have trust data for docker.io/mariadb/server

Additional information you deem important (e.g. issue happens only occasionally):
Setting DOCKER_CONTENT_TRUST_SERVER=https://notary.docker.io works, but adding a 443 port leads to a HTTP 503 response. Using port 4443 instead leads to connection refused (I believe this is the wrong port anyway).

Output of docker version:

Client:
 Version:           18.09.5
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        e8ff056
 Built:             Thu May  9 23:11:19 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.09.5
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       e8ff056
  Built:            Thu May  9 22:59:19 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Activity

  1. thaJeztah commented on Jun 14, 2019

    @thaJeztah
    Member

    Thanks for reporting; I'm able to reproduce this.

    Wondering if it's an issue in the client, or if there's a configuration issue with the hosted notary server 🤔

    /cc @justincormack ptal

  2. peterthomassen commented on Jun 14, 2019

    @peterthomassen
    Author

    The two requests should be identical, with the exception of the Host header that likely contains the port only in one case.

  3. thaJeztah commented on May 14, 2026

    @thaJeztah
    Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions