Images

DockerHub Availability

Juno container images are publicly available on DockerHub for direct access. You can pull images directly from our DockerHub repository without any special requests or approval process. To launch Genesis, you will need to provide the license key during the deployment process.

Air-Gapped Environments

If you are deploying in an air-gapped environment, you will need to follow the manual image deployment steps below to download and load images into your private registry.

Below you can find images that you will need to ingest for an airgapped deployment.

It tracks latest releases of our charts:

• Genesis
• Orion

The deployment also leverages a few upstream components:

• ArgoCD
• ingress-nginx

If your cluster has those pre-deployed or if you prefer to manage those yourself, it is likely they will work out of the box. The above versions are what we actively test our air-gapped deployment against and what we recommend - they are not technically a hard requirement.

Image Name	Component	Image Version
docker.io/junoinnovations/genesis	Juno Genesis	v4.0.0.beta.1
docker.io/junoinnovations/titan	Juno Genesis	v2.1.1
docker.io/junoinnovations/terra	Juno Genesis	v2.1.0
docker.io/junoinnovations/hubble	Juno Orion	v5.0.0-beta.1
docker.io/junoinnovations/kuiper	Juno Orion	v4.0.0-beta.2
docker.io/junoinnovations/rhea	Juno system wide	v1.0.0
registry.k8s.io/ingress-nginx/controller	ingress-nginx	v1.15.0
registry.k8s.io/ingress-nginx/kube-webhook-certgen	ingress-nginx	v1.6.8
quay.io/argoproj/argocd	ArgoCD	v3.0.9
ghcr.io/dexidp/dex	ArgoCD	v2.41.1
docker.io/library/redis	ArgoCD	7.2.7-alpine

When using our workload images, we recommend you pull the latest stable tag of Helios. The workload image is not included in the list above, since there are multiple choices - we ship multiple distros and flavors that serve different industry-specific use cases.

Here are the provided links for 3^rd party air-gapped guides:

• Nvidia GPU Operator

Setting up a basic images repository

To setup a basic image registry for storing and pulling the above list of containers we can use a variety of software, the below guide makes use of the Registry container

1. Pull and run the registry container specifying a local path for persistent storage

   1. docker run -d \
        -p 5000:5000 \
        --restart=always \
        --name registry \
        -v /mnt/registry:/var/lib/registry \
        registry:3
      

2. Pull an image locally (I'll use genesis as an example here but this will need to be repeated for the full list of images above)
   1. docker pull docker.io/junoinnovations/genesis:v4.0.1.beta.1
3. Tag the downloaded image pointing to the local registry, change localhost to the IP/hostname of the deployed registry container if not on the same host.
   1. docker tag docker.io/junoinnovations/genesis:v4.0.1.beta.1 localhost:5000/juno-innovations/genesis:v4.0.1.beta.1
4. Push the newly tagged container to the local registry
   1. docker push localhost:5000/juno-innovations/genesis:v4.0.1.beta.1
5. (Optional) Test it has worked by attempting to pull the image from the registry
   1. docker pull localhost:5000/juno-innovations/genesis:v4.0.1.beta.1