Open koppor opened 2 years ago
Same issue. Were you able to solve?
Switching to the amd64 Alpine image instead of i386 and using wine64 resolved the "Bad EXE" errors for me.
Switching to the amd64 Alpine image instead of i386 and using wine64 resolved the "Bad EXE" errors for me.
I'm having the same problem but I'm not very fluent in Docker just yet, how would I go about doing this?
I'm having the same problem but I'm not very fluent in Docker just yet, how would I go about doing this?
Check out my fork https://github.com/n-stein/backblaze-personal-wine where you can see the updated Dockerfile.
Download the source code from there and unzip it. Build the image yourself like this:
docker build -t backblaze-wine:latest -f /path/to/downloaded/Dockerfile
Then just adjust your docker compose yml to use image: backblaze-wine
You can also run the image directly rather than using docker-compose (which is what I do since I use Podman instead of Docker):
run_args=(
--name=backblaze
-v $HOME/programs/backblaze:/wine
-v $HOME/programs/nextcloud/data:/data
-v $HOME/backups:/data/backups
-p 5900:5900
--restart=unless-stopped
-d backblaze-wine
)
docker run "${run_args[@]}"
Note this image also fixes the broken characters by installing missing msttcore fonts.
Ok, I think I got it built correctly, but when I connect to the VNC server I'm met with a box saying Wine could not find a wine-mono package which is needed for .NET applications. It offers to download one but if I click the download button it displays a progress bar which doesn't move at all and nothing happens unless I click cancel, at which point it loops back to the error message.
Thanks for your help so far, I hope I'm not being too much of a pest!
When starting the container, I get the following output:
When placing the
install_backblaze.exe
manually in that folder, I get following outputs:The screen is "OKish":
Should I need to worry about the broken characters?