Programatically push cde images to a registry

DrissiReda

In containerized execution I can prepare the base container image and push it to a registry so that containerized execution pods will pull the image directly from my container.

However for cde image I can build it using dssadmin build-base-image —type cde

But I cannot push it to a registry. I found a command that does nothing with an exit code 0:

dsscli container-exec-base-images-push

Is that normal? Is it supposed to happen?

Any other functional way to push locally built images to registry?

Turribeach

Check all the options of the dssadmin build-base-image command as you can add an option to push the images to the repository as well in the same command.

yonghyun

dssadmin build-base-image —type cde

위와 같은 명령어로 baseimage를 만들 수 있습니다.

dsscli container-exec-base-images-push

위 명령어가 동작하는지는 확인하지못하였습니다.

위 명령어가 동작하려면 push할 레파지토리에 올릴 수 있는 정보가 dss서버에 저장이 되어있거나
올릴 수 있는 상태가 되어야 할 것으로 보여집니다.

위 방법 대신에 수동으로 레파지토리에 push를 할 수 있습니다.

1. 레파지토리에 로그인
[dataiku@vbox dss_data]$ docker login docker.io/yonghyun3221/dss
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Authenticating with existing credentials for docker.io/yonghyun3221/dss
Existing credentials are valid. Already logged in to docker.io

2. 생성된 이미지 확인 < e5fd08a1825e 사용 할 것>
docker images
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
REPOSITORY TAG IMAGE ID CREATED SIZE
<none> <none> e5fd08a1825e 3 minutes ago 2.76 GB
localhost/dku-cde-base-ityrplrkwtls8regn8cralpy dss-13.1.4 a9bf1db8405f 2 weeks ago 5.26 GB
docker.io/library/nginx latest 9bea9f2796e2 3 months ago 196 MB
docker.io/library/almalinux 8 f1218159f16a 5 months ago 196 MB

3. 이미지 테그
podman tag e5fd08a1825e yonghyun3221/dss:latest

4. 이미지 push

podman push yonghyun3221/dss:latest
Getting image source signatures
Copying blob a9af2451b55c done |
Copying blob 52e288afc9fc done |
Copying blob 4d70471a4d9b done |
Copying blob 62cd0e5682e7 done |
Copying blob 44f0fb6f61ec done |
Copying blob 2609da11fd88 skipped: already exists
Copying blob bf1d9e1d3a4c done |
Copying blob 269abf47d47e done |
Copying blob 9ea2e6a97fb0 done |
Copying blob e8b8f6023e1a done |
Copying blob 49d1432dc306 done |
Copying blob b6b7bf85c697 done |
Copying blob 8c438a6fbf6c done |
Copying blob 2eb45e798a2e done |
Copying blob d62bd2740451 done |
Copying blob 060427fa7745 done |
Copying blob 8f74ee1f97f7 done |
Copying blob 5ad49c1fd910 done |
Copying blob fae7e275d619 done |
Copying blob b6a34af9750c done |
Copying blob 4ab83e03723c done |
Copying config e5fd08a182 done |
Writing manifest to image destination

podman 대신 docker를 사용해서도 가능합니다

정상적으로 push된 것을 확인

Turribeach

I believe this post will help you too:

Custom script for Container execution to push the base images

Shridhar

Mar 19, 2025

I'm running into an error ''' Error while checking kubernetes logs, returned 1 Error from server (BadRequest): container "c" in pod "dataiku-exec-python-afmkmmh" is waiting to start: image can't be pulled '''

The main reason here is because of the access issue for pushing the image to the internal repository. I was checking the custom script option but how do I use it to push the existing image to internal repo.

Any sample 'custom script' for this —> settings - container execution - configuration?

Operating system used: Linux

Operating system used: Linux

Operating system used: Linux

Operating system used: Linux

Operating system used: Linux

---

View Post