Skip to content

Conversation

warjiang
Copy link
Contributor

@warjiang warjiang commented Aug 6, 2025

What type of PR is this?

Allow to deploy coze-studio use private docker registry as an alternative of public docker registry. Just set REGISTRY environment variable, it will work out.

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Add documentation if the current PR requires user awareness at the usage level.

(Optional) Translate the PR title into Chinese.

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):

(Optional) Which issue(s) this PR fixes:

@fanlv
Copy link
Collaborator

fanlv commented Aug 6, 2025

是不是通过 docker 配置也可以指定走 私有库?

比如配置daemon.json {"registry-mirrors": ["https://b4a1f63a156e435f9aeb797bdf515250.mirror.swr.myhuaweicloud.com"]}

@warjiang
Copy link
Contributor Author

warjiang commented Aug 6, 2025

是不是通过 docker 配置也可以指定走 私有库?

比如配置daemon.json {"registry-mirrors": ["https://b4a1f63a156e435f9aeb797bdf515250.mirror.swr.myhuaweicloud.com"]}

yes, you're right. For images that will be downloaded from docker.io can use this way to config private registry. I think declare the registry in an explicit way will make it more clearly. Using registry-mirrors or insecure-registries, there will be two limits:

  • for those images that will not be downloaded from docker.io, registry-mirrors or insecure-registries will not work
  • the config for private registry can't be unified(for example containerd or podman)
    for some users that will use containerd, the config will like
     [plugins."io.containerd.grpc.v1.cri".registry]
       [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
         [plugins."io.containerd.grpc.v1.cri".registry.mirrors."my-registry.local:5000"]
           endpoint = ["http://my-registry.local:5000"] 
       [plugins."io.containerd.grpc.v1.cri".registry.configs]
         [plugins."io.containerd.grpc.v1.cri".registry.configs."my-registry.local:5000".auth]
           username = "user"
           password = "pass"
         [plugins."io.containerd.grpc.v1.cri".registry.configs."my-registry.local:5000".tls]
           insecure_skip_verify = true
    for some users that will use podman, the config will like
     [[registry]]
     prefix = "my-registry.local:5000"
     location = "my-registry.local:5000"
     insecure = true

@warjiang warjiang changed the title feat(docker): add support for private registry feat(infra): add support for private registry Aug 8, 2025
@warjiang warjiang force-pushed the feat/support-private-registry branch from ca4ca4a to f4d7f44 Compare August 15, 2025 03:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants