Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offline Deployment: When running manage-offline-container-images.sh with setting the DESTINATION_REGISTRY environment variable, container images is not registered in the container registry specified by DESTINATION_REGISTRY. #11867

Open
DearJey opened this issue Jan 7, 2025 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@DearJey
Copy link

DearJey commented Jan 7, 2025

What happened?

I tried to register a container image with using the script file and command below during offline construction, registry container will be created and the image will be registered there even though there is an existing container registry.

# export DESTINATION_REGISTRY=WWW.XXX.YYY.ZZZ:5000 #Specify an existing container registry
# ./manage-offline-container-images.sh register
  • after running script
# podman ps -a
CONTAINER ID  IMAGE                              COMMAND               CREATED        STATUS      PORTS                   NAMES
7a0be471fd1c  docker.io/library/registry:2.8.2   /etc/docker/regis...  7 hours ago    Up 7 hours  0.0.0.0:5000->5000/tcp  docker-distribution #an existing container registry
f9a88bd70ff8  docker.io/library/nginx:alpine     nginx -g daemon o...  6 hours ago    Up 6 hours  0.0.0.0:8080->80/tcp    nginx
721be2b0607b  docker.io/library/registry:latest  /etc/docker/regis...  2 minutes ago  Created     0.0.0.0:5000->5000/tcp  registry #created

What did you expect to happen?

I expected the image to be registered in the existing container registry.

How can we reproduce it (as minimally and precisely as possible)?

[Node configuration]

  • Offline
controlplane1
worker1
  • Online(Preparation)
workstation(podman, docker-distribution)

[Version]

  • Kubespray Version: v2.25.0
  • Docker version: v26.1

OS

Linux 5.14.0-427.13.1.el9_4.x86_64 x86_64
NAME="Red Hat Enterprise Linux"
VERSION="9.4 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.4"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.4 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.4
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.4"

Version of Ansible

ansible [core 2.16.13]
config file = None
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.11/site-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.11.7 (main, Jan 22 2024, 00:00:00) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] (/usr/bin/python3.11)
jinja version = 3.1.4
libyaml = True

Version of Python

Python 3.9.18

Version of Kubespray (commit)

v2.25.0

Network plugin used

calico

Full inventory with variables

None

Command used to invoke ansible

None

Output of ansible run

None

Anything else we need to know

No response

@DearJey DearJey added the kind/bug Categorizes issue or PR as related to a bug. label Jan 7, 2025
@DearJey DearJey changed the title Offline Deployment: When setting the DESTINATION_REGISTRY environment variable and run manage-offline-container-images.sh, container images is not registered in the container registry specified by DESTINATION_REGISTRY. Offline Deployment: When running manage-offline-container-images.sh with setting the DESTINATION_REGISTRY environment variable, container images is not registered in the container registry specified by DESTINATION_REGISTRY. Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant