K
Q

Create a new image from a container’s changes in Google Cloud Container

11/24/2017

I have an Image which i should add a dependency to it. Therefore I have tried to change the image when is running on the container and create new Image. I have follow this article with the following commands after :

kubectl run my-app --image=gcr.io/my-project-id/my-app-image:v1 --port 8080
kubectl get pods
kubectl exec -it my-app-container-id -- /bin/bash

then in the shell of container, i have installed the dependency using "pip install NAME_OF_Dependncy". Then I have exited from the shell of container and as it have been explained in the article, i should commit the change using this command :

sudo docker commit CONTAINER_ID nginx-template

But I can not find the corresponding command for Google Kubernetes Engine with kubectl

How should i do the commit in google container engine?

-- Majico
docker
google-cloud-platform
google-kubernetes-engine
kubernetes

Similar Questions

how to control access for pods/exec only in kubernetes rbac without pods create binded?
kubernetes jenkins-plugins - JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior
API auth error connecting Prometheus to Kubernetes (Openshift Origin)
Kubernetes API Access from Pod

1 Answer

11/24/2017

As with K8s Version 1.8. There is no way to do Hot Fix changes directly to the images.For example, Committing new image from running container. If you still change or add something by using exec it will stay until the container is running. It's not best practice in K8s eco-system.

The recommended way is to use Dockerfile and customise the images according to the necessity and requirements.After that, you can push that images to the registry(public/ private ) and deploy it with K8s manifest file.

Solution to your issue

  • Create a Dockerfile for your images.
  • Build the image by using Dockerfile.
  • Push the image to the registry.
  • write the deployment manifest file as well service manifest file.
  • apply the manifest file to the k8s cluster.

Now If you want to change/modify something, you just need to change/modify the Dockerfile and follow the remaining steps.

As you know that containers are a short living creature which does not have persist changed behaviour ( modified configuration, changing file system).Therefore, It's better to give new behaviour or modification at the Dockerfile.

Kubernetes Mantra
Kubernetes is Cloud Native product which means it does not matter whether you are using Google Cloud, AWS or Azure. It needs to have consistent behaviour on each cloud provider.

-- Suresh Vishnoi
Source: StackOverflow