invoiceninja / dockerfiles

Docker files for Invoice Ninja
https://hub.docker.com/r/invoiceninja/invoiceninja
GNU General Public License v2.0
399 stars 263 forks source link

Docker Desktop v4.15.0 on mac M1 - permission problems #474

Closed nottavi closed 1 year ago

nottavi commented 1 year ago

Setup information docker-compose

Describe the bug I have clone the latest version. I've updated Docker Desktop to its last version v4.15.0 on my Macbook Air M1. As I had problem on other project I stayed on osfx as file sharing implementation.

I did change permission in docker/app directory as mentioned in the documentation.

When launching with docker-compose up -d the _app container keep on restarting due to this error message repeating quite several times:

cp: can't create directory '/var/www/app/storage/app': Permission denied

Expected behavior _app container running ;)

Screenshots/logs

Capture d’écran 2022-12-06 à 13 31 46
Any Error that sucks

Docker/Kubernetes/Helm:

Server: Docker Desktop 4.15.0 (93002) Engine: Version: 20.10.21 API version: 1.41 (minimum version 1.12) Go version: go1.18.7 Git commit: 3056208 Built: Tue Oct 25 17:59:41 2022 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.10 GitCommit: 770bd0108c32f3fb5c73ae1264f7e503fe7b2661 runc: Version: 1.1.4 GitCommit: v1.1.4-0-g5fd4c4d docker-init: Version: 0.19.0 GitCommit: de40ad0



Kind regards
turbo124 commented 1 year ago

I'd try changing the permissions on the directory to suit the docker desktop user, it may be running under its own user rather than the assumed "user" which is the local user account (ie you)

nottavi commented 1 year ago

Thx

I've changed the permission with my user:group - docker seems running with this user. It got better but still got some blocking errors. The container seems to run but I only got the index loaded and some ressources can't be loaded, so i get a grey page only

I will try to redo the installation process later ... I have no other containers running

Capture d’écran 2022-12-07 à 08 27 42
turbo124 commented 1 year ago

do you have in your env file TRUSTED_PROXIES=*

nottavi commented 1 year ago

Yes I had it like this TRUSTED_PROXIES='*' Tried with TRUSTED_PROXIES=* and got the same results (sorry Docker Desktop on Mac M1 is starting to make me mad !) - everything was working well before I upgraded to the last version of Docker Desktop

I think I should try to add an entry in my /etc/hosts (and clean it cause it contains a lot of lines)

nottavi commented 1 year ago

@turbo124 finally made it works. Was expecting to have the app runing under http://in.localhost:8003 and finally it is running on port 80.

And it may be obvious, but I didn't rename env file to .env :(