Giters

tom300z / backblaze-personal-wine

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Bad EXE format

koppor opened this issue · comments

commented

When starting the container, I get the following output:

backblaze-personal-wine    | Downloading the Backblaze personal installer...
backblaze-personal-wine    | Connecting to www.backblaze.com (104.17.5.3:443)
backblaze-personal-wine    | wget: error getting response: Connection reset by peer
backblaze-personal-wine    | Backblaze installer started, please go through the graphical setup in by logging onto the containers vnc server
backblaze-personal-wine    | wine: cannot find '/wine//drive_c/install_backblaze.exe'
backblaze-personal-wine    | Installation finished or aborted, trying to start the Backblaze client...
backblaze-personal-wine    | Backblaze not installed
backblaze-personal-wine    | Initializing the wine prefix
backblaze-personal-wine    | wine: configuration in '/wine' has been updated.
backblaze-personal-wine    | unlink: can't remove file '/wine//dosdevices/z:': No such file or directory
backblaze-personal-wine    | ln: /wine//dosdevices/d:/data: File exists
backblaze-personal-wine    | Setting the wine computer name
backblaze-personal-wine    | The operation completed successfully
backblaze-personal-wine    | The operation completed successfully
backblaze-personal-wine    | The operation completed successfully
backblaze-personal-wine    | Downloading the Backblaze personal installer...

When placing the install_backblaze.exe manually in that folder, I get following outputs:

backblaze-personal-wine    | Backblaze installer started, please go through the graphical setup in by logging onto the containers vnc server
backblaze-personal-wine    | wine: Bad EXE format for C:\Program Files\Backblaze\x64\bztransmit64.exe.
backblaze-personal-wine    | wine: Bad EXE format for C:\Program Files\Backblaze\x64\bzfilelist64.exe.
backblaze-personal-wine    | wine: Bad EXE format for C:\Program Files\Backblaze\x64\bztransmit64.exe.
backblaze-personal-wine    | wine: Unhandled page fault on read access to 0x0000000c at address 0x4babd3 (thread 00d3), starting debugger...

The screen is "OKish":

grafik

Should I need to worry about the broken characters?

commented

Same issue. Were you able to solve?

commented

Switching to the amd64 Alpine image instead of i386 and using wine64 resolved the "Bad EXE" errors for me.

commented

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?

commented

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.

commented

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!