首页 > 解决方案 > 在本地 Openshift 错误中部署 docker.io 映像

问题描述

我正在尝试从 docker.io "docker.io/library/jboss-webserver54-openjdk11-tomcat9-openshift-rhel7:latest" 部署一个图像并且它给出一个错误,它也发生在其他图像上。它给了我错误:

you may not have access to the container image "docker.io/library/jboss-webserver54-openjdk11-tomcat9-openshift-rhel7:latest"

我在代理后面,所以也许这就是问题所在,也许我必须登录到 docker 或在 Openshift 中启用某些东西。

有没有人这个问题或可以指出一个可能的解决方案?

我在 Web 控制台和命令行中遇到了同样的问题:

在此处输入图像描述

W1105 09:56:34.086973   15624 dockerimagelookup.go:300] container image remote registry lookup failed: you may not have access to the container image "docker.io/library/jboss-webserver54-openjdk11-tomcat9-openshift-rhel7:latest"
error:  local file access failed with: CreateFile jboss-webserver54-openjdk11-tomcat9-openshift-rhel7: The system cannot find the file specified.
error: unable to locate any images in image streams, templates loaded in accessible projects, template files, local docker images with name "jboss-webserver54-openjdk11-tomcat9-openshift-rhel7"

Argument 'jboss-webserver54-openjdk11-tomcat9-openshift-rhel7' was classified as an image, image~source, or loaded template reference.

The 'oc new-build' command will match arguments to the following types:

  1. Images tagged into image streams in the current project or the 'openshift' project
     - if you don't specify a tag, we'll add ':latest'
  2. Images in the container registry, on remote registries, or on the local container engine
  3. Git repository URLs or local paths that point to Git repositories

--allow-missing-images can be used to force the use of an image that was not matched

谢谢!

标签: springdockertomcatopenshiftredhat

解决方案


推荐阅读