Podman unable to run on Azure Kubernetes pods #16658
Replies: 4 comments
-
Without podman info it is hard to help you. |
Beta Was this translation helpful? Give feedback.
-
@Luap99 I was able to overcome that issue by setting the security context in the pod to run in privileged mode. However like you mentioned, I cannot run with any storage driver as I get the below error.
Even if I run with aufs driver, I get the below error.
Posting the podman info that you requested below
Please have a look into it |
Beta Was this translation helpful? Give feedback.
-
The logs in debug mode is attached for your reference root@826afae58f5f:/# podman run --log-level=debug --events-backend=file docker.io/nginx DEBU[0000] container "ccc718aef92879557d9a1cb0cc33fe2a673aef4c04180dc1c57bf979c1aa3149" has run directory "/run/containers/storage/aufs-containers/ccc718aef92879557d9a1cb0cc33fe2a673aef4c04180dc1c57bf979c1aa3149/userdata" |
Beta Was this translation helpful? Give feedback.
-
After changing the storage driver, execute |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Briefly describe the problem you are having in a few paragraphs.
I am intending to run podman inside a kubernetes pod whose base image shall be debian/ubuntu
I have created a Dockerfile thus with base image as Ubuntu/Debian/mcr.microsoft.com/dotnet/sdk:6
Running the same in my local machine and creating a container from the Dockerfile with podman installed, lets me create a container and run inside the container which runs on WSL ubuntu. The same when run on Azure VM or Azure Kubernetes ndoes gives me the below error.
Steps to reproduce the issue:
Create a VM in Azure with OS as ubuntu
Build an image using below Dockerfile and create a container using this image. Try to run a new container inside the container.
PS: The commented lines in the Dockerfile was required when I ran in WSL. Kept it commented for reference. I am sure this has something to do with the storage driver based on some other issues I observed. I tried to specify drivers like Overlay, Overlayfs which do not exists in the underlying VM, but need guidance to how overcome.
Describe the results you received:
Describe the results you expected:
Container is created and runs fine inside kubernetes pod that runs on Azure VM's
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Unable to obtain, however should be latest. Gives me same above error running version
Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Beta Was this translation helpful? Give feedback.
All reactions