New issue
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
Can't use tmpfs
as runroot for containers
#8772
Comments
Can you set |
I set
Still doesn't work, it returns the same error:
|
You also need to set driver="overlay" |
This works, but the
Am I misunderstanding this config?
Shouldn't this config cause the runtime to be there? The mounts seem to still be in my home folder:
|
can you look under |
That's where it is, but shouldn't it be in |
no. The storage files are stored under Usually XDG_RUNTIME_DIR is on tmpfs, so it would be very expensive to have the storage there. |
As I understand, the storage files, like the images/layers itself should be in the graphroot. But I thought Am I wrong about that? If so, how can I move that into my |
Why do you want them on your tmpfs? The upper/work directories can grow quite large and run out of space on a tmpfs mount. |
For speed 😁 I don't need a lot of storage during runtime, I'd rather have speed. I mostly manually mount, Also, I got 32GiB, often have more than 10GiB free 😅 So, there is no setting for runtime only? Only the complete graphroot? So, what does |
runroot is used to store the state of running containers. Another possibility if you'd like to keep the upper layers on tmpfs is to use an additional RO store. The RO store can be placed on the persistent storage, while the main store is on the tmpfs |
Mh, read-only doesn't sound like a drop-in configuration 😅 I think I'll stick with the current system, it's not like it's slow 😁 Thanks for your help though! 😊 |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Cannot use
tmpfs
as runroot for containersSteps to reproduce the issue:
$XDG_RUNTIME_DIR
as tmpfs[storage].runroot
:Describe the results you received:
Describe the results you expected:
A working podman
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: