I think it is too much additional equipment and IT-Support only for a intermediate step without any really necessary functionality.
I think there’s a misconception here. It really requires no special equipment or setup to create a simple local registry. If you know what to do it takes maybe a minute at most. As an example here’s what many of our other customers do:
# This command starts a container that acts as a simple registry on your machine
$ docker run -d -p 5000:5000 --restart=always --name registry registry:2
# Now you can tag and push your image to this regisry like so
$ docker push localhost:5000/my-image
# Now with a compose file like this
$ cat docker-compose.yml
version: '2.4'
services:
test:
image: localhost:5000/my-image
# You can run the bundle command targeting this local registry
$ torizoncore-builder bundle --dind-param="--insecure-registry=localhost:5000" docker-compose.yml
Creating Docker Container bundle...
Starting DIND container
Using Docker host "tcp://127.0.0.1:22376"
Connecting to Docker Daemon at "tcp://127.0.0.1:22376"
Fetching container image localhost:5000/my-image
Pulling from my-image
2db29710123e: Pull complete
Digest: sha256:f54a58bc1aac5ea1a25d796ae155dc228b3f0e11d046ae276b39c4bf2f13d8c4
Status: Downloaded newer image for localhost:5000/my-image:latest
Saving Docker Compose file
Exporting storage
Storing container bundle into "bundle"
Stopping DIND container
Successfully created Docker Container bundle in "bundle"!
It’s as simple as that. Most of the instructions regarding the local registry were adapted from the official Docker documentation here: Registry | Docker Docs
Best Regards,
Jeremias