Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Need help installing backblaze-personal-wine docker on my DS1821+

#1
I'm trying to set up the backblaze-personal-wine docker as outlined in the NAS Compares article on the subject.  (I tried to post the link here but I'm told I can't post URLs.)
I'm able to pull and start the container, but the Backblaze client doesn't seem to install.  Looking at the log there are several instances of "wine: /wine is not owned by you".  I assume this is preventing the container from creating needed folder structures but I am not super familiar with Docker and I don't know how to resolve this.  Can anyone help?

Thanks in advance!
Reply
#2
(07-30-2023, 09:13 PM)Davel23 Wrote: I'm trying to set up the backblaze-personal-wine docker as outlined in the NAS Compares article on the subject.  (I tried to post the link here but I'm told I can't post URLs.)
I'm able to pull and start the container, but the Backblaze client doesn't seem to install.  Looking at the log there are several instances of "wine: /wine is not owned by you".  I assume this is preventing the container from creating needed folder structures but I am not super familiar with Docker and I don't know how to resolve this.  Can anyone help?
Thanks in advance!
Fix the wine: /wine is not owned by you error by ensuring the /wine directory is owned by the correct UID/GID:
sudo chown -R 1000:1000 /path/to/wine
Replace 1000:1000 with the container's user ID.
Run with UID/GID:
docker run --user $(id -u):$(id -g) -v /path/to/wine:/wine backblaze-personal-wine
Use Docker Compose:
Add user: "1000:1000" to your docker-compose.yml
Reply
#3
(07-30-2023, 09:13 PM)Davel23 Wrote: I'm trying to set up the backblaze-personal-wine docker as outlined in the NAS Compares article on the subject.  (I tried to post the link here but I'm told I can't post URLs.)
I'm able to pull and start the container, but the Backblaze client doesn't seem to install.  cookie clicker unblocked Looking at the log there are several instances of "wine: /wine is not owned by you".  I assume this is preventing the container from creating needed folder structures but I am not super familiar with Docker and I don't know how to resolve this.  Can anyone help?

Thanks in advance!

The error "wine: /wine is not owned by you" means the Docker container's user (usually root) doesn't match your host user ID.  The solution: run the container with `--user $(id -u):$(id -g)` to specify your host user ID and group ID.  For example: `docker run -it --user $(id -u):$(id -g) -v /your/data/directory:/wine <image_name>`. This gives the container your host user ID and mounts your data directory to `/wine` inside the container, fixing the permission issue. Replace `<image_name>` and `/your/data/directory` with your actual values. This is safer than changing permissions inside the container.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)