That’d be nice.
For anyone facing the same issue, be aware that containers that are stuck this way keep restarting:
pi@raspberrypi:~ $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[...]
6e728b2712ef storjlabs/storagenode:bfc3d4c9d-v1.52.2-go1.17.5 "/entrypoint --log.o…" 14 seconds ago Restarting (2) 2 seconds ago storj_node_2
[...]
storj_watchtower
So unless you manually create the folder just after starting the node while it is still setting itself up (downloading binaries), you may have to issue the command several times before it succeeds.
Let me illustrate:
pi@raspberrypi:~ $ sudo docker exec -it storj_node_2 mkdir /var/log/supervisor
Error response from daemon: Container 66309508bb99470998ce2c4b1162a20b61d369c865bd3ff03c316105c2fadff4 is restarting, wait until the container is running
pi@raspberrypi:~ $ sudo docker exec -it storj_node_2 mkdir /var/log/supervisor
Error response from daemon: Container 66309508bb99470998ce2c4b1162a20b61d369c865bd3ff03c316105c2fadff4 is restarting, wait until the container is running
[...]
pi@raspberrypi:~ $ sudo docker exec -it storj_node_2 mkdir /var/log/supervisor
Error response from daemon: Container 66309508bb99470998ce2c4b1162a20b61d369c865bd3ff03c316105c2fadff4 is restarting, wait until the container is running
pi@raspberrypi:~ $ sudo docker exec -it storj_node_2 mkdir /var/log/supervisor
pi@raspberrypi:~ $
Thanks again @baker for your quick and effective reply