Laurent Goderre

How are you mounting your data? Are you doing it the way shown in the documentation in the Volumes section? https://hub.docker.com/_/drupal

In your Dockerfile, you don't explicitly set a user so the `RUN mkdir /tmp/files` runs as root. SInce in hyour use case you don't necessarily know the id or group...

Yeah, the symlink also needs its permission expanded. There seems to be something weird about the `ls` commandf though. The following Dockerfile yields this result ``` FROM php:8.1-apache RUN mkdir...

> The modern function of the sticky bit refers to directories, and protects directories and their content from being hijacked by non-owners; this is found in most modern Unix-like systems....

The purpose is to prevent PHP, a general purpose language, from being able to perform destructive operations on the filesystem if an attacker is able to inject malicious code that...

The use case that this support is running the container as another user that therefore doesn't have permission to modify the data.

Im curious as to why you are using the architecture namespace instead of `docker run -it --rm --pull always debian` or `docker run -it --rm --pull always docker.io/debian`

Not that this only affects version 3.11 and under. Version 3.12 is not affected.

A simple docker kill should work ``` % docker run -d --rm --name postgres-kill -e POSTGRES_PASSWORD=1234 postgres bffde2d477d889715f4344d90e62b0bad023ac94b6bd1ea6a262814340d86dfd % docker kill postgres-kill postgres-kill ``` or ``` % docker run -d...

I am not using a signal, just forcing the container to be destroyed ``` % docker run -d --rm --name postgres-kill -e POSTGRES_PASSWORD=1234 postgres time docker kill postgres-kill aee271f8ce85eff0b80bdb64ba4db83a1571c17bd963b664ca6365dc8296cf8f postgres-kill...