backblaze-personal-wine icon indicating copy to clipboard operation
backblaze-personal-wine copied to clipboard

Issues building Dockerfile

Open unifiedcommsguy opened this issue 3 years ago • 2 comments

I'm having issues building your Dockerimage from the dockerfile included.

I get errors regarding permissions. Is your docker image hosted in docker hub different from the code in the repo?

Thanks for your help.

unifiedcommsguy avatar Oct 23 '21 02:10 unifiedcommsguy

Can you share the exact error message? The docker hub image was directly built from this repo so there should be no differences

tom300z avatar Oct 23 '21 02:10 tom300z

The container seems to start ok, VNC fires up, Backblaze binary is downloaded, and the wine started, however, I get this error:

the installer could not communicate with https://ca000.backblaze.com so installation failed. Fix your internet connection

When I look at the console I see a bunch of errors that do not occur with your image (not the below logs are from a container using my image and the previous persistent /wine path)

Starting the virtual display & vnc server 
 
 --- x11vnc loop: 1 --- 
 
cp: can't stat '/wine//drive_c/Program Files/Backblaze/bzbui.exe.aside': No such file or directory 
unlink: can't remove file '/wine//dosdevices/z:': No such file or directory 
Setting the wine computer name 
The XKEYBOARD keymap compiler (xkbcomp) reports: 
> Warning:          Could not resolve keysym XF86BrightnessAuto 
> Warning:          Could not resolve keysym XF86DisplayOff 
> Warning:          Could not resolve keysym XF86Info 
> Warning:          Could not resolve keysym XF86AspectRatio 
> Warning:          Could not resolve keysym XF86DVD 
> Warning:          Could not resolve keysym XF86Audio 
> Warning:          Could not resolve keysym XF86ChannelUp 
> Warning:          Could not resolve keysym XF86ChannelDown 
> Warning:          Could not resolve keysym XF86Break 
> Warning:          Could not resolve keysym XF86VideoPhone 
> Warning:          Could not resolve keysym XF86ZoomReset 
> Warning:          Could not resolve keysym XF86Editor 
> Warning:          Could not resolve keysym XF86GraphicsEditor 
> Warning:          Could not resolve keysym XF86Presentation 
> Warning:          Could not resolve keysym XF86Database 
> Warning:          Could not resolve keysym XF86Voicemail 
> Warning:          Could not resolve keysym XF86Addressbook 
> Warning:          Could not resolve keysym XF86DisplayToggle 
> Warning:          Could not resolve keysym XF86SpellCheck 
> Warning:          Could not resolve keysym XF86ContextMenu 
> Warning:          Could not resolve keysym XF86MediaRepeat 
> Warning:          Could not resolve keysym XF8610ChannelsUp 
> Warning:          Could not resolve keysym XF8610ChannelsDown 
> Warning:          Could not resolve keysym XF86Images 
> Warning:          Could not resolve keysym XF86NotificationCenter 
> Warning:          Could not resolve keysym XF86PickupPhone 
> Warning:          Could not resolve keysym XF86HangupPhone 
> Warning:          Could not resolve keysym XF86Fn 
> Warning:          Could not resolve keysym XF86Fn_Esc 
> Warning:          Could not resolve keysym XF86FnRightShift 
> Warning:          Could not resolve keysym XF86Numeric0 
> Warning:          Could not resolve keysym XF86Numeric1 
> Warning:          Could not resolve keysym XF86Numeric2 
> Warning:          Could not resolve keysym XF86Numeric3 
> Warning:          Could not resolve keysym XF86Numeric4 
> Warning:          Could not resolve keysym XF86Numeric5 
> Warning:          Could not resolve keysym XF86Numeric6 
> Warning:          Could not resolve keysym XF86Numeric7 
> Warning:          Could not resolve keysym XF86Numeric8 
> Warning:          Could not resolve keysym XF86Numeric9 
> Warning:          Could not resolve keysym XF86NumericStar 
> Warning:          Could not resolve keysym XF86NumericPound 
> Warning:          Could not resolve keysym XF86NumericA 
> Warning:          Could not resolve keysym XF86NumericB 
> Warning:          Could not resolve keysym XF86NumericC 
> Warning:          Could not resolve keysym XF86NumericD 
> Warning:          Could not resolve keysym XF86CameraFocus 
> Warning:          Could not resolve keysym XF86WPSButton 
> Warning:          Could not resolve keysym XF86CameraZoomIn 
> Warning:          Could not resolve keysym XF86CameraZoomOut 
> Warning:          Could not resolve keysym XF86CameraUp 
> Warning:          Could not resolve keysym XF86CameraDown 
> Warning:          Could not resolve keysym XF86CameraLeft 
> Warning:          Could not resolve keysym XF86CameraRight 
> Warning:          Could not resolve keysym XF86AttendantOn 
> Warning:          Could not resolve keysym XF86AttendantOff 
> Warning:          Could not resolve keysym XF86AttendantToggle 
> Warning:          Could not resolve keysym XF86LightsToggle 
> Warning:          Could not resolve keysym XF86ALSToggle 
> Warning:          Could not resolve keysym XF86Buttonconfig 
> Warning:          Could not resolve keysym XF86Taskmanager 
> Warning:          Could not resolve keysym XF86Journal 
> Warning:          Could not resolve keysym XF86ControlPanel 
> Warning:          Could not resolve keysym XF86AppSelect 
> Warning:          Could not resolve keysym XF86Screensaver 
> Warning:          Could not resolve keysym XF86VoiceCommand 
> Warning:          Could not resolve keysym XF86Assistant 
> Warning:          Could not resolve keysym XF86BrightnessMin 
> Warning:          Could not resolve keysym XF86BrightnessMax 
> Warning:          Could not resolve keysym XF86KbdInputAssistPrev 
> Warning:          Could not resolve keysym XF86KbdInputAssistNext 
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgroup 
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgroup 
> Warning:          Could not resolve keysym XF86KbdInputAssistAccept 
> Warning:          Could not resolve keysym XF86KbdInputAssistCancel 
> Warning:          Could not resolve keysym XF86RightUp 
> Warning:          Could not resolve keysym XF86RightDown 
> Warning:          Could not resolve keysym XF86LeftUp 
> Warning:          Could not resolve keysym XF86LeftDown 
> Warning:          Could not resolve keysym XF86RootMenu 
> Warning:          Could not resolve keysym XF86MediaTopMenu 
> Warning:          Could not resolve keysym XF86Numeric11 
> Warning:          Could not resolve keysym XF86Numeric12 
> Warning:          Could not resolve keysym XF86AudioDesc 
> Warning:          Could not resolve keysym XF863DMode 
> Warning:          Could not resolve keysym XF86NextFavorite 
> Warning:          Could not resolve keysym XF86StopRecord 
> Warning:          Could not resolve keysym XF86PauseRecord 
> Warning:          Could not resolve keysym XF86VOD 
> Warning:          Could not resolve keysym XF86Unmute 
> Warning:          Could not resolve keysym XF86FastReverse 
> Warning:          Could not resolve keysym XF86SlowReverse 
> Warning:          Could not resolve keysym XF86Data 
> Warning:          Could not resolve keysym XF86OnScreenKeyboard 
> Warning:          Could not resolve keysym XF86PrivacyScreenToggle 
> Warning:          Could not resolve keysym XF86SelectiveScreenshot 
> Warning:          Could not resolve keysym XF86Macro1 
> Warning:          Could not resolve keysym XF86Macro2 
> Warning:          Could not resolve keysym XF86Macro3 
> Warning:          Could not resolve keysym XF86Macro4 
> Warning:          Could not resolve keysym XF86Macro5 
> Warning:          Could not resolve keysym XF86Macro6 
> Warning:          Could not resolve keysym XF86Macro7 
> Warning:          Could not resolve keysym XF86Macro8 
> Warning:          Could not resolve keysym XF86Macro9 
> Warning:          Could not resolve keysym XF86Macro10 
> Warning:          Could not resolve keysym XF86Macro11 
> Warning:          Could not resolve keysym XF86Macro12 
> Warning:          Could not resolve keysym XF86Macro13 
> Warning:          Could not resolve keysym XF86Macro14 
> Warning:          Could not resolve keysym XF86Macro15 
> Warning:          Could not resolve keysym XF86Macro16 
> Warning:          Could not resolve keysym XF86Macro17 
> Warning:          Could not resolve keysym XF86Macro18 
> Warning:          Could not resolve keysym XF86Macro19 
> Warning:          Could not resolve keysym XF86Macro20 
> Warning:          Could not resolve keysym XF86Macro21 
> Warning:          Could not resolve keysym XF86Macro22 
> Warning:          Could not resolve keysym XF86Macro23 
> Warning:          Could not resolve keysym XF86Macro24 
> Warning:          Could not resolve keysym XF86Macro25 
> Warning:          Could not resolve keysym XF86Macro26 
> Warning:          Could not resolve keysym XF86Macro27 
> Warning:          Could not resolve keysym XF86Macro28 
> Warning:          Could not resolve keysym XF86Macro29 
> Warning:          Could not resolve keysym XF86Macro30 
> Warning:          Could not resolve keysym XF86MacroRecordStart 
> Warning:          Could not resolve keysym XF86MacroRecordStop 
> Warning:          Could not resolve keysym XF86MacroPresetCycle 
> Warning:          Could not resolve keysym XF86MacroPreset1 
> Warning:          Could not resolve keysym XF86MacroPreset2 
> Warning:          Could not resolve keysym XF86MacroPreset3 
> Warning:          Could not resolve keysym XF86KbdLcdMenu1 
> Warning:          Could not resolve keysym XF86KbdLcdMenu2 
> Warning:          Could not resolve keysym XF86KbdLcdMenu3 
> Warning:          Could not resolve keysym XF86KbdLcdMenu4 
> Warning:          Could not resolve keysym XF86KbdLcdMenu5 
Errors from xkbcomp are not fatal to the X server 
 --- x11vnc loop: waiting for: 55 
 
Xlib:  extension "DPMS" missing on display ":0". 
PORT=5900 
 
The VNC desktop is:      backblaze-b9b59c8ff-l4btl:0 
wine: configuration in L"wine" has been updated. 
wine: could not open working directory L"unix\\", starting in the Windows directory. 
reg: The operation completed successfully 
wine: could not open working directory L"unix\\", starting in the Windows directory. 
reg: The operation completed successfully 
wine: could not open working directory L"unix\\", starting in the Windows directory. 
reg: The operation completed successfully 
Backblaze found, starting the Backblaze client... 
wine: could not open working directory L"unix\\", starting in the Windows directory. 

As a comparison, these are the startup logs from your image:


Starting the virtual display & vnc server 
cp: can't stat '/wine//drive_c/Program Files/Backblaze/bzbui.exe.aside': No such file or directory 
unlink: can't remove file '/wine//dosdevices/z:': No such file or directory 
Setting the wine computer name 
 
 --- x11vnc loop: 1 --- 
 
 --- x11vnc loop: waiting for: 31 
 
Xlib:  extension "DPMS" missing on display ":0". 
 
The VNC desktop is:      backblaze-59d59c9896-mvjhc:0 
PORT=5900 
wine: configuration in '/wine' has been updated. 
The operation completed successfully 
The operation completed successfully 
The operation completed successfully 
Backblaze found, starting the Backblaze client... 

I believe the original error to be DNS related, but this does not occur with your image.

I'm not certain why I am receiving all the XKEYBOARD warnings either as they don't occur either.

The only thing I can think of is perhaps your version was compiled earlier and the newer versions of the alpine packages may need some adjustments.

unifiedcommsguy avatar Oct 23 '21 06:10 unifiedcommsguy