You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No, not the usual permission problem related to user and group permissions.
With INIT_ASSETS=0 the container starts and I can write to the assets folder in an interactive session (docker exec -it homer /bin/sh).
I believe it's this issue here: alpinelinux/docker-alpine#156
The test in entrypoint.sh wrongly detects the folder as not writeable when in fact it is.
It is probably not happening on you regular Linux server, but I am testing it on an M1 Mac (where Homer is usally not used I guess) ;).
Here are some screenshots demonstrating it:
Only changing INIT_ASSETS:
The text was updated successfully, but these errors were encountered:
No, not the usual permission problem related to user and group permissions.
With
INIT_ASSETS=0
the container starts and I can write to the assets folder in an interactive session (docker exec -it homer /bin/sh
).I believe it's this issue here: alpinelinux/docker-alpine#156
The test in
entrypoint.sh
wrongly detects the folder as not writeable when in fact it is.It is probably not happening on you regular Linux server, but I am testing it on an M1 Mac (where Homer is usally not used I guess) ;).
Here are some screenshots demonstrating it:
Only changing
INIT_ASSETS
:The text was updated successfully, but these errors were encountered: