We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to the docs, I should be able to specify some options when creating a tmpfs mount - https://docs.podman.io/en/latest/markdown/podman-run.1.html#tmpfs-fs
I've specified these in the nomad job file as:
tmpfs = [ "/tmp/csi/keys:rw,size=1000k" ]
But it seems not to be working, when I podman container inspect directly I get:
podman container inspect
... "Tmpfs": { "/tmp/csi/keys:rw,size=1000k": "rw,rprivate,nosuid,nodev,tmpcopyup" }, ...
Which rather suggests that it's mounted a folder named /tmp/csi/keys:rw,size=1000k rather than /tmp/csi/keys
/tmp/csi/keys:rw,size=1000k
/tmp/csi/keys
I'm very new to this, so maybe I'm missing something obvious...
The text was updated successfully, but these errors were encountered:
Hi @LordAro 👋
Thanks for the report. I think we're missing logic here to split the input string into destination and options.
nomad-driver-podman/driver.go
Lines 1359 to 1365 in 259a211
I will try to to push a fix next week.
Sorry, something went wrong.
Just tripped over this myself tonight trying to get the Ceph CSI driver running, looks like the parser is still doing the simple operation here.
lgfa29
No branches or pull requests
According to the docs, I should be able to specify some options when creating a tmpfs mount - https://docs.podman.io/en/latest/markdown/podman-run.1.html#tmpfs-fs
I've specified these in the nomad job file as:
But it seems not to be working, when I
podman container inspect
directly I get:Which rather suggests that it's mounted a folder named
/tmp/csi/keys:rw,size=1000k
rather than/tmp/csi/keys
I'm very new to this, so maybe I'm missing something obvious...
The text was updated successfully, but these errors were encountered: