Help with Troubleshooting

[amino-8]

I've managed to get mediacms up and running on docker using the named-volumes.yaml compose file.
mediacms is sitting behind a reverse proxy and seems to work ok apart from the admin page. It lokos like somethign can't be accessed on the backend (shown in the screenshot). Can somepoint point me in the direction of where I should be looking to troubleshoot the issue.

[amino-8]

In terms of the static directory I have it pointed to ./static so it should pick up the default one that's created by the git clone and the migrations container seems to complete successfully.

[amino-8]

After a bit more trouble shooting, I tried to run mediacms using the standard docker-compose and it worked perfectly. What it looks like is that it copied a bunch more files into static. This means if I run the named-volumes.yaml against the newly populated static directory it also works perfectly.
Does this mean there's an issue with the migrations container populating the static folder if using named volumes or could it be a permissions issue? (The permissions on static have not changed between the two runs).

[amino-8]

Looks like it's already been covered here. I thought I searched properly!

[amino-8]

#586