From 23ca913a403605546b8f6ebafbd98040a09f0c8c Mon Sep 17 00:00:00 2001
From: thegoodlittlescript
 <51981126+thegoodlittlescript@users.noreply.github.com>
Date: Thu, 2 Feb 2023 08:41:28 -0700
Subject: [PATCH] Note the bug in tmpfs permissions

There is an open bug in tmpfs that results in permissions being reset on container restart. At this point it has tripped up quite a few people. This adds a hint about the issue, and a link to a the workaround we ultimately used (a functionality not mentioned elsewhere in the docs).
---
 storage/tmpfs.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/storage/tmpfs.md b/storage/tmpfs.md
index ed3640e420..91b5aea31e 100644
--- a/storage/tmpfs.md
+++ b/storage/tmpfs.md
@@ -28,6 +28,7 @@ persist in either the host or the container writable layer.
 * Unlike volumes and bind mounts, you can't share `tmpfs` mounts between
 containers.
 * This functionality is only available if you're running Docker on Linux.
+* Setting permissions on tmpfs may still suffer from a bug causing them to [reset after container restart](https://github.com/docker/for-linux/issues/138). In some cases [setting the uid/gid](https://github.com/docker/compose/issues/3425#issuecomment-423091370) can serve as a workaround.
 
 ## Choose the --tmpfs or --mount flag