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'm not sure if it's a bug or if I'm just doing it incorrectly, but it seems that arguments on the create pod details tab aren't being passed through on creation.
For example, I'm trying to pass -p 8080:80 to the pod on creation and it doesn't work.
I've tried all variations like p 8080:80, p=8080:80 etc and none of them are applied on creation. When I create a pod via CLI with podman pod create -p 8080:80 --name test-pod, podman ps -a -p correctly shows that the pod has those ports bound to it. I tried doing it under the infra tab as well and neither work or apply any options.
The text was updated successfully, but these errors were encountered:
Looks like arguments rather get passed to command inside container, see pics.
The application probably needs some way to pass custom parameters to podman run command, like, for example, to pass gpu device (--device nvidia.com/gpu=all --security-opt=label=disable) or to choose container network (--network example-network).
I'm using Pods (v2.0.3) via Flatpak on Fedora 41.
I'm not sure if it's a bug or if I'm just doing it incorrectly, but it seems that arguments on the create pod details tab aren't being passed through on creation.
For example, I'm trying to pass
-p 8080:80
to the pod on creation and it doesn't work.I've tried all variations like
p 8080:80
,p=8080:80
etc and none of them are applied on creation. When I create a pod via CLI withpodman pod create -p 8080:80 --name test-pod
,podman ps -a -p
correctly shows that the pod has those ports bound to it. I tried doing it under the infra tab as well and neither work or apply any options.The text was updated successfully, but these errors were encountered: