Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible permission issue? #106

Open
devanteweary opened this issue Feb 1, 2024 · 15 comments
Open

Possible permission issue? #106

devanteweary opened this issue Feb 1, 2024 · 15 comments

Comments

@devanteweary
Copy link

Hey there again!

Long story short, in the previous version I was able to run "wine explorer" and "wine xkill" with no problem.

Since updating, this is what I get when I run them...

root@441dd3aed297:/tmp# wine explorer
wine: '/config/wine' is not owned by you

root@441dd3aed297:/tmp# wine xkill
wine: '/config/wine' is not owned by you

That's about it!

@traktuner
Copy link
Collaborator

Hey,
could you please post your docker run command and the full docker logs?
Thank you!

@devanteweary
Copy link
Author

Sorry was busy weekend! Here goes!

Docker Run Command 👈
docker run
  -d
  --name='Backblaze_Personal_Backup'
  --net='bridge'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Devante-NAS"
  -e HOST_CONTAINERNAME="Backblaze_Personal_Backup"
  -e 'SECURE_CONNECTION'='0'
  -e 'TZ'='America/Los_Angeles'
  -e 'DISPLAY_WIDTH'='1280'
  -e 'DISPLAY_HEIGHT'='1024'
  -e 'VNC_PASSWORD'=''
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'X11VNC_EXTRA_OPTS'=''
  -e 'ENABLE_CJK_FONT'=''
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:5800]/'
  -l net.unraid.docker.icon='/mnt/user/Media/Images/Icons/Backblaze.png'
  -p '5800:5800/tcp'
  -p '5900:5900/tcp'
  -v '/mnt/user/':'/drive_d/':'rw'
  -v '/mnt/user/appdata/Backblaze_Personal_Backup':'/config':'rw'
  --init
  --restart=unless-stopped
  --log-driver=syslog
  --log-opt tag={{.Name}}
  --log-opt syslog-address=udp://192.168.1.200:1514 'tessypowder/backblaze-personal-wine'
b4e8e99bc9980a19ad0bec46b66154efc11db4b1a45b70ff62216119ac922838

The command finished successfully!

And I'm not 100% sure what you mean by full Docker logs so I included two things:

  1. My syslog of the container from the last 24 hours: syslog.zip

  2. The log that shows up when I click the container 👇

Container Log 👈

[cont-init ] 15-cjk-font.sh: executing...
[cont-init ] 15-cjk-font.sh: terminated successfully.
[cont-init ] 15-install-pkgs.sh: executing...
[cont-init ] 15-install-pkgs.sh: terminated successfully.
[cont-init ] 85-take-config-ownership.sh: executing...
[cont-init ] 85-take-config-ownership.sh: terminated successfully.
[cont-init ] 89-info.sh: executing...
╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
│ │
│ Application: Backblaze Personal Backup │
│ Application Version: n/a │
│ Docker Image Version: n/a │
│ Docker Image Platform: linux/amd64 │
│ │
╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
[cont-init ] 89-info.sh: terminated successfully.
[cont-init ] all container initialization scripts executed.
[init ] giving control to process supervisor.
[supervisor ] loading services...
[supervisor ] loading service 'default'...
[supervisor ] loading service 'app'...
[supervisor ] loading service 'gui'...
[supervisor ] loading service 'certsmonitor'...
[supervisor ] service 'certsmonitor' is disabled.
[supervisor ] loading service 'nginx'...
[supervisor ] loading service 'xvnc'...
[supervisor ] loading service 'openbox'...
[supervisor ] loading service 'logmonitor'...
[supervisor ] service 'logmonitor' is disabled.
[supervisor ] loading service 'logrotate'...
[supervisor ] all services loaded.
[supervisor ] starting services...
[supervisor ] starting service 'xvnc'...
[xvnc ] Xvnc TigerVNC 1.13.1 - built Dec 21 2023 00:39:59
[xvnc ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc ] Underlying X server release 12014000
[xvnc ] Sun Feb 4 08:21:36 2024
[xvnc ] vncext: VNC extension running!
[xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900
[xvnc ] vncext: created VNC server for screen 0
[supervisor ] starting service 'nginx'...
[nginx ] Listening for HTTP connections on port 5800.
[supervisor ] starting service 'openbox'...
[supervisor ] starting service 'app'...
[app ] + cat /RELEASE_VERSION
[app ] + release_version=v1.6
[app ] + local_version_file=/config/wine//dosdevices/c:/ProgramData/Backblaze/bzdata/bzreports/bzserv_version.txt
[app ] + install_exe_path=/config/wine//dosdevices/c:/
[app ] + log_file=/config/wine//dosdevices/c:/backblaze-wine-startapp.log
[app ] + custom_user_agent=backblaze-personal-wine/v1.6 (JonathanTreffler, +https://github.com/JonathanTreffler/backblaze-personal-wine-container), CFNetwork
[app ] + pinned_bz_version_file=/PINNED_BZ_VERSION
[app ] + sed -n 1p /PINNED_BZ_VERSION
[app ] + pinned_bz_version=9.0.0.749
[app ] + sed -n 2p /PINNED_BZ_VERSION
[app ] + pinned_bz_version_url=https://web.archive.org/web/20231218152237/https://secure.backblaze.com/win32/install_backblaze.exe
[app ] + export WINEARCH=win64
[app ] + disclaimer_updatemode
[app ] + [ false = true ]
[app ] + [ false = true ]
[app ] + echo FORCE_LATEST_UPDATE is disabled. Using known-good version of Backblaze.
[app ] FORCE_LATEST_UPDATE is disabled. Using known-good version of Backblaze.
[app ] + [ -f /config/wine/drive_c/Program Files (x86)/Backblaze/bzbui.exe ]
[app ] + [ false = true ]
[app ] + [ false = true ]
[app ] + [ -f /config/wine//dosdevices/c:/ProgramData/Backblaze/bzdata/bzreports/bzserv_version.txt ]
[app ] + log_message UPDATER: FORCE_LATEST_UPDATE=false, Checking if newer version than /config/wine//dosdevices/c:/ProgramData/Backblaze/bzdata/bzreports/bzserv_version.txt is available.
[app ] + date
[app ] + echo Sun 04 Feb 2024 08:21:38 AM PST: UPDATER: FORCE_LATEST_UPDATE=false, Checking if newer version than /config/wine//dosdevices/c:/ProgramData/Backblaze/bzdata/bzreports/bzserv_version.txt is available.
[app ] + cat /config/wine//dosdevices/c:/ProgramData/Backblaze/bzdata/bzreports/bzserv_version.txt
[app ] + local_version=9.0.0.749
[app ] + compare_versions 9.0.0.749 9.0.0.749
[app ] + local_version=9.0.0.749
[app ] + compare_version=9.0.0.749
[app ] + dpkg --compare-versions 9.0.0.749 lt 9.0.0.749
[app ] + log_message UPDATER: COMPARE: no new version found - local 9.0.0.749 - remote 9.0.0.749
[app ] + date
[app ] + echo Sun 04 Feb 2024 08:21:38 AM PST: UPDATER: COMPARE: no new version found - local 9.0.0.749 - remote 9.0.0.749
[app ] + return 1
[app ] + log_message UPDATER: FORCE_LATEST_UPDATE=false, The local version is up to date. There may be a newer version available when using FORCE_LATEST_UPDATE=true
[app ] + date
[app ] + echo Sun 04 Feb 2024 08:21:38 AM PST: UPDATER: FORCE_LATEST_UPDATE=false, The local version is up to date. There may be a newer version available when using FORCE_LATEST_UPDATE=true
[app ] + start_app
[app ] + log_message STARTAPP: Starting Backblaze version /config/wine//dosdevices/c:/ProgramData/Backblaze/bzdata/bzreports/bzserv_version.txt
[app ] + date
[app ] + echo Sun 04 Feb 2024 08:21:38 AM PST: STARTAPP: Starting Backblaze version /config/wine//dosdevices/c:/ProgramData/Backblaze/bzdata/bzreports/bzserv_version.txt
[app ] + sleep infinity
[app ] + wine64 /config/wine/drive_c/Program Files (x86)/Backblaze/bzbui.exe -noqiet
[supervisor ] all services started.

Hope this is what you wanted!

Thank you!

@traktuner
Copy link
Collaborator

Thank you!
Could you please try the :ubuntu22 tag instead of latest and try it again? (latest will only be updated when we push out a new versioned release)
I pushed out a new build last week. The fix was related to start apps like winecfg etc. Maybe it also helps with your issue.
Please let me know!

@devanteweary
Copy link
Author

Thank you! Could you please try the :ubuntu22 tag instead of latest and try it again? (latest will only be updated when we push out a new versioned release) I pushed out a new build last week. The fix was related to start apps like winecfg etc. Maybe it also helps with your issue. Please let me know!

Hey @traktuner , I tried to add the :ubuntu22 tag but it gave me "Failed to run command" upon re-saving the container settings.
Just a reminder, I'm on Unraid.

Currently not using any :latest tag by the way. My repository is tessypowder/backblaze-personal-wine

Oh one more thing, not sure if it's related but I've always had this error that has to do with permissions so maybe it's connected?

image

OK thank you and sorry I didn't get Ubuntu tag working!

@traktuner
Copy link
Collaborator

Hey,
the bzreports permission error is not related and can be ignored, backup works anyway.
I don't use unraid personally, but I think when you edit the repository (edit the container) you then append the tag
tessypowder/backblaze-personal-wine:ubuntu22

@xela1
Copy link
Contributor

xela1 commented Feb 5, 2024

are you running docker exec as the 'app' user or root?

docker exec --user app -it container_name bash

might work?

@devanteweary
Copy link
Author

Hey, the bzreports permission error is not related and can be ignored, backup works anyway. I don't use unraid personally, but I think when you edit the repository (edit the container) you then append the tag tessypowder/backblaze-personal-wine:ubuntu22

Yessir that's exactly what I did and got that "Failed to run command" upon saving it with that tag.

are you running docker exec as the 'app' user or root?

docker exec --user app -it container_name bash

might work?

Hmmm not 100% sure. I don't really "run" anything.
I just installed the 'app' from the Community repo (i.e. app store) in Unraid.
Then set it up using the container settings below and set it to auto-run on boot (which I rarely reboot).

I also tried running it with Privileged mode enabled but no change.

@xela1
Copy link
Contributor

xela1 commented Feb 5, 2024

How are you running these though

root@441dd3aed297:/tmp# wine explorer
wine: '/config/wine' is not owned by you

root@441dd3aed297:/tmp# wine xkill
wine: '/config/wine' is not owned by you

@devanteweary
Copy link
Author

devanteweary commented Feb 5, 2024

How are you running these though

root@441dd3aed297:/tmp# wine explorer
wine: '/config/wine' is not owned by you

root@441dd3aed297:/tmp# wine xkill
wine: '/config/wine' is not owned by you

Ooooh gotcha sorry!

I'm dropping into the console and running them.

  • In Unraid: Docker tab > Click Backblaze_Personal_Container > Click Console > type those above commands

I also try running it outside on the container's console.

  • In Unraid: Click console icon > Type docker exec --user app Backblaze_Personal_Backup wine explorer

That's the one I usually did that has worked before the last update.

@xela1
Copy link
Contributor

xela1 commented Feb 5, 2024

In Unraid: Click console icon > Type docker exec --user app Backblaze_Personal_Backup wine explorer

and this isn't working? Can you paste the output from this one, as it shouldn't look like your example:

root@441dd3aed297:/tmp# wine explorer
wine: '/config/wine' is not owned by you

@devanteweary
Copy link
Author

OK just tried both explorer and xkill.

explorer just kind of does nothing. The cursor goes down to the next line with no text until I CTRL+C it.

xkill gives me the following:

Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

Oh and for reference, in the past I would run Explorer for whatever reason, and then use xkill to close it since there is no X/close button.

@xela1
Copy link
Contributor

xela1 commented Feb 5, 2024

In Unraid: Click console icon > Type docker exec --user app Backblaze_Personal_Backup wine xkill

should be

In Unraid: Click console icon > Type docker exec --user app Backblaze_Personal_Backup xkill

@devanteweary
Copy link
Author

In Unraid: Click console icon > Type docker exec --user app Backblaze_Personal_Backup wine xkill

should be

In Unraid: Click console icon > Type docker exec --user app Backblaze_Personal_Backup xkill

Oh interesting! Wonder why it changed.
OK trying it without the "wine"...

  • xkill> xkill: unable to open display""
  • explorer> OCI runtime exec failed: exec failed: unable to start container process: exec: "Explorer": executable file not found in $PATH: unknown

@traktuner
Copy link
Collaborator

Yessir that's exactly what I did and got that "Failed to run command" upon saving it with that tag.

Sorry to hear. There has to be a way to not use the latest tag.
xkill (and all other commands) works for me with the :ubuntu20 and :ubuntu22 tag flawlessly (but not latest) - with the default user root. no need to user "app".

@devanteweary
Copy link
Author

Yessir that's exactly what I did and got that "Failed to run command" upon saving it with that tag.

Sorry to hear. There has to be a way to not use the latest tag. xkill (and all other commands) works for me with the :ubuntu20 and :ubuntu22 tag flawlessly (but not latest) - with the default user root. no need to user "app".

OK well thank you for replying. Yeah not sure why that tag isn't working for me but I'll hang in there and maybe there'll be a fix or something one day. :P'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants