@malcolmlewis1 Yes and no, yes we want to use our own repository eventually, and your link helps with that. but that’s not what I’m currently struggling with.
Currently, I have RKE up and running. Here are the steps I currently take to run a simple Hello World test
- mkdir nginx
- cd nginx
- echo “<h1>Hello World from NGINX!!” > index.html
- vim Dockerfile
FROM nginx:alpine COPY . /usr/share/nginx/html
- docker build --tag nginx-helloworld:latest .
- kubectl run hello-world --image=nginx-helloworld:latest --image-pull-policy=Never --port=80
- kubectl port-forward pods/hello-world 8080:80
- curl localhost:8080
What I want to do is the following
- mkdir nginx
- cd nginx
- echo “<h1>Hello World from NGINX!!” > index.html
- vim Dockerfile
FROM nginx:alpine COPY . /usr/share/nginx/html
- podman build --tag nginx-helloworld:latest .
- kubectl run hello-world --image=nginx-helloworld:latest --image-pull-policy=Never --port=80
- kubectl port-forward pods/hello-world 8080:80
- curl localhost:8080
This doesn’t work in its current configuration. As kubectl does not know how to pull from the local Podman repository.
Leaving RKE in its current installation, can I make changes to the local-cluster.yaml to point kubectl to the podman repo instead of Docker? So that when I run kubectl run hello-world --image=nginx-helloworld:latest it pulls from the Podman built images and not the Docker images.
As I mentioned, we don’t care of Rancher is using Docker, as long as the pods created within the cluster are Podman built images.
Or perhaps there is a way within a manifest file, when I use Kubectl apply?