admin管理员组

文章数量:1023699

In the past I have skipped the port when specifying images in .gitlab-ci.yml.

some-build-job:
  stage: build
  image: server/image:tag

After a new gitlab installation I have to add the port.

some-build-job:
  stage: build
  image: server:5000/image:tag

Is there a place where the default port can be set to 5000 such that it can be omitted in the image name when writing ci scripts as before?

It is a local gitlab installation in an isolated docker network. Is the origin of the problem maybe that ssh access to the registry is not enabled? If ssh access is enabled then the client (i.e. the runner) may be looking at port 443 by default and then the problem would disappear by itself?

In the past I have skipped the port when specifying images in .gitlab-ci.yml.

some-build-job:
  stage: build
  image: server/image:tag

After a new gitlab installation I have to add the port.

some-build-job:
  stage: build
  image: server:5000/image:tag

Is there a place where the default port can be set to 5000 such that it can be omitted in the image name when writing ci scripts as before?

It is a local gitlab installation in an isolated docker network. Is the origin of the problem maybe that ssh access to the registry is not enabled? If ssh access is enabled then the client (i.e. the runner) may be looking at port 443 by default and then the problem would disappear by itself?

本文标签： default port 5000 for image specifications in gitlabciymlStack Overflow

版权声明：本文标题：default port 5000 for image specifications in .gitlab-ci.yml - Stack Overflow 内容由热心网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://it.en369.cn/questions/1745588642a2157753.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。