Custom Docker Images 1

In this section, we will modify the docker image for the Ubuntu 18.04 application image.

Modify Docker Image

In this section, we modify the Ubuntu 18.04 application Docker image defaultImageRepoTag so that we can provide a custom Docker image.

Currently defaultImageRepoTag is set to bluedata/ubuntu18.04:1.1

Change defaultImageRepoTag to localhost:5000/myubuntu:1.0 (we will create this image in the steps below).

The full json should now look like this:

{
"apiVersion": "kubedirector.hpe.com/v1beta1",
"kind": "KubeDirectorApp",
"metadata": {
"name" : "ubuntu18x"
},
"spec" : {
"systemdRequired": true,
"defaultPersistDirs" : ["/home", "/var"],
"config": {
"roleServices": [
{
"serviceIDs": [
"ssh"
],
"roleID": "vanilla_ubuntu"
}
],
"selectedRoles": [
"vanilla_ubuntu"
]
},
"label": {
"name": "Ubuntu 18.04",
"description": "Ubuntu 18.04 with no preinstalled apps"
},
"distroID": "bluedata/ubuntu18x",
"version": "1.1",
"configSchemaVersion": 8,
"services": [
{
"endpoint": {
"port": 22,
"isDashboard": false
},
"id": "ssh",
"label": {
"name": "SSH"
}
}
],
"defaultImageRepoTag": "localhost:5000/myubuntu:1.0",
"defaultConfigPackage": null,
"roles": [
{
"cardinality": "1+",
"id": "vanilla_ubuntu"
}
]
}
}

Create Dockerfile

We need to create a Dockerfile - let's create a new folder for it inside deploy/example_catalog/ called myubuntu:

Now create a Dockerfile in the folder myubuntu with the contents:

FROM bluedata/ubuntu18.04:1.1
RUN touch /modified_by_yourname

Change yourname to your name without spaces or special characters.

Run a local registry

To make development easier, we will deploy a local registry to push our custom image to:

docker run -d -p 5000:5000 --restart=always --name registry registry:2

Build and Push image

In the terminal, change to the myubuntu folder and build your custom image and push it to the local registry:

docker build --tag myubuntu:1.0 .
docker tag myubuntu:1.0 localhost:5000/myubuntu:1.0

Next we push the image to our local registry:

docker push localhost:5000/myubuntu:1.0

Deploy the KD app image

First ensure you aren't still running an Ubuntu KD clusters from the previous tutorial.

kubectl delete kubedirectorclusters.kubedirector.hpe.com ubuntu18.04-persistent

Next undeploy the existing Ubuntu KD application image definition:

kubectl delete kubedirectorapps.kubedirector.hpe.com ubuntu18x

Deploy the new Ubuntu KD application with your changes:

kubectl apply -f ../cr-app-ubuntu18.04.json

Check the deployement was successful:

kubectl get kubedirectorapps.kubedirector.hpe.com

You can see my image has only just been deployed:

NAME AGE
...
tensorflow-gpu-jupyter 18h
training-engine 18h
ubuntu18x 47s

Deploy the KD Cluster

Next we can deploy the KD Cluster:

kubectl apply -f ../../example_clusters/cr-cluster-ubuntu18.04-stor.yaml

We can then run ls / inside the cluster to see the file we created in our Docker image modified_by_yourname:

$ kubectl exec -it kdss-w6jj7-0 -- /bin/bash
root@kdss-w6jj7-0:/# ls /
bin boot dev etc home lib lib64 media mnt modified_by_yourname opt proc root run sbin srv sys tmp usr var

Reference information

In this lesson we saw how defaultImageRepoTag works.

You can find the:

  • KubeDirectorApp definition here
  • KubeDirectorApp.spec definition here

If a KD Application has multiple roles (covered later), you can specify the imageRepoTag for each role:

  • KubeDirectorApp.role definition here
Edit this page