black screen since update to most recent version #99
Comments
|
Please add the logs of the docker container (docker logs [container name]) |
|
Seeing the same behaviour in unraid container. I'm on main, but assume digest is same as v1.6 based on timing. |
Having same issues on my Unraid container also. |
|
Also worth a try: Unfortunately I can not reproduce this - I have no Unraid system. |
|
Not sure if this helps I have tried renaming the xdg folder and having the docker recreate it I also provided full permissions to the folders for the docker I still get a black screen. I even deleted the docker and tried reinstalling from scratch and get the black screen. My docker log is below. The error indicates a permissions issue but to me it looks like it timed out maybe? [cont-init ] 89-info.sh: terminated successfully. |
|
For what it's worth; this portion: ...is exactly what I see and have mentioned in #98. |
Hi, thanks for the help. I ended up restoring the container from a backup, before I saw your response. It went through a reinstall of mono and started working again. Thanks again for your help. Love this container btw! |
|
I don't think this is actually fixed. A fresh install hits this for me too. (Complete with the black screen and permission denied message). Trying v1.5 instead worked though. Worked: Failed: |
Hey, In addition - yould you please use the latest tag and --privileged in your docker command?
Thank you! |
|
I'm using Windows 10 w/ Linux containers on Docker. (Honestly I was just testing this out for future usage.. since of course I can use the app directly on Windows). I cleared the config directory then ran: Then i opened localhost:8080 in chrome to a black screen:
|
|
@csm10495 The permissions of your config directory are not correctly configured, that is why it cannot install Backblaze. I have no idea how docker permissions on Windows work, but on linux that directory has to belong to the same uid and gid as specified in the USER_ID and GROUP_ID env variables of the docker. |
|
How's that possible? It creates the config/ directory on my desktop. I delete it every time before running. Then it creates it. If it could create it, I figure it could download the installer. |
|
The Docker daemon creates the directory to have a mountpoint for the volume, not our docker itself. |
|
Odd. Like you said: works. The thing I don't get is without those new params, the config/ directory gets made and things get filled in: If it was just an empty dir, i understand your theory.. but how could it have made files in the dir if it didn't have permission? |
Great to hear that it's working now! edit: typo |
|
Exactly, but in most cases you would want to lower the required permissions for startapp and wine, by changing the permissions of the config directory instead of giving it higher privileges. --privileged should not be necessary, if you have set UID and GID to 0, we have only seen that help on some Synology devices, but in general that is far higher privilege than required. |
Hello,
Seeing only a black screen when accessing the web interface since updating to the most recent version. Any ideas?
The text was updated successfully, but these errors were encountered: