microsoft
Samba dependency issue during docker vm creation process
Been trying to find a way around this issue, one of the packages in the dockerfile is samba and for some reason the connection fails when trying to pull it even though debian trixie repo has it
this is what i see in the log 12.29 Ign:38 http://deb.debian.org/debian trixie/main amd64 samba-common-bin amd64 2:4.21.4+dfsg-1 16.35 Err:38 http://deb.debian.org/debian trixie/main amd64 samba-common-bin amd64 2:4.21.4+dfsg-1 16.35 Error reading from server. Remote end closed connection [IP: 151.101.126.132 80]
i've tried changing from scratch to ubuntu:latest i've tried changing the repo to https i've tried removing samba from the docker file and adding it post container creation (this worked but after everything was set up the tool could not interact with the VM, the vm was accessible in the gradio ui but it would error after sending a prompt stating the vm was not accessible)
Any thoughts?
ok well i found a way around the issue by wget the samba deb file and installing it via the docker file BUT still having issues even though samba is now installed i'm getting a ERROR: Samba daemon failed to start! during the image creation process. the VM loads just fine but the control server does not. boo.....
Ok so for anyone else who is having this weird issue. you can exclude Samba from your Docker File and move the scrip folders from omnibox\vm\win11setup to the windows docker VM. Then just update all the variables in those scripts that have the script folder set to \host.lan\Data to a location local on the VM where the scripts/config files are located. Then run the scripts in order of install.bat then setup.ps1