From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Filip Schauer <f.schauer@proxmox.com>
Subject: applied: [pve-devel] [PATCH container] lxc config: mount /dev/shm tmpfs for application containers
Date: Tue, 19 May 2026 22:17:39 +0200 [thread overview]
Message-ID: <177922185765.2558480.12587747856006374554.b4-ty@b4> (raw)
In-Reply-To: <20251202152733.204787-1-f.schauer@proxmox.com>
On Tue, 02 Dec 2025 16:27:28 +0100, Filip Schauer wrote:
> Mount a tmpfs at /dev/shm into containers without an init system which
> would normally set up a shared memory filesystem. This satisfies the OCI
> Runtime Spec [0], which specifies that the following should be made
> available in the container:
> /proc proc
> /sys sysfs
> /dev/pts devpts
> /dev/shm tmpfs
>
> [...]
Applied, thanks!
[1/1] lxc config: mount /dev/shm tmpfs for application containers
commit: a535b4cba0e90999cb9d41530b4e6180d1f3f8b9
prev parent reply other threads:[~2026-05-19 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 15:27 [pve-devel] [PATCH container] lxc config: mount /dev/shm tmpfs for application containers Filip Schauer
2026-01-15 10:08 ` Fabian Grünbichler
2026-05-19 20:17 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177922185765.2558480.12587747856006374554.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=f.schauer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox