You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am new in podman world, and I have a question when using podman with kubernetes:
I have an image built with command "podman build -t podman-microservice . , and this creates successfully an image. I can use podman run for creating a container using the previous image I created, and I can access to this container fine.
The problem comes when I try to use Kind and I create a manifest file to define a pod:
Content of app.yaml with the manifest defining my pod:
apiVersion: v1
kind: Pod
metadata:
name: demo-app
labels:
app: demo-app
spec:
containers:
- name: app-service
image: localhost/podman-microservice:latest
ports:
- name: http
containerPort: 8080
protocol: TCP
If I execute: kubectl apply -f app.yaml, it creates the pod, but if I go to podman desktop, it tells that pod is in warning status, and it is unable to retrieve the image. It tells failed to pull and unpack image "localhost/podman-microservice:latest": failed to resolve reference "localhost/podman-microservice:latest": failed to do request: Head "http://localhost/v2/podman-microservicio/manifests/latest": dial tcp 127.0.0.1:80: connect: connection refused.
How can I specify the local image that I created?
Why with podman run it finds the image, but not with kubectl manifest?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I am new in podman world, and I have a question when using podman with kubernetes:
Content of app.yaml with the manifest defining my pod:
apiVersion: v1
kind: Pod
metadata:
name: demo-app
labels:
app: demo-app
spec:
containers:
- name: app-service
image: localhost/podman-microservice:latest
ports:
- name: http
containerPort: 8080
protocol: TCP
If I execute: kubectl apply -f app.yaml, it creates the pod, but if I go to podman desktop, it tells that pod is in warning status, and it is unable to retrieve the image. It tells failed to pull and unpack image "localhost/podman-microservice:latest": failed to resolve reference "localhost/podman-microservice:latest": failed to do request: Head "http://localhost/v2/podman-microservicio/manifests/latest": dial tcp 127.0.0.1:80: connect: connection refused.
How can I specify the local image that I created?
Why with podman run it finds the image, but not with kubectl manifest?
Thanks a lot!
Best regards!
Beta Was this translation helpful? Give feedback.
All reactions