Closed highlyunavailable closed 3 years ago
Hello,
I had the same issue.
It seems that windbg is not being maintain anymore. I used windows-sdk-10-version-2004-windbg instead, and it works fine for building the image (ue4-build-prerequisites:2004).
Apologies for the delay in responding to this issue, I've been inordinately busy over the past couple of months and I'm only now making my way through my GitHub backlog.
Thanks for reporting this, I'll investigate the use of the alternate Chocolatey package and update ue4-docker ASAP.
Okay, preliminary testing in a Windows Server Core version 1809 container confirms that the newer SDK package (windows-sdk-10-version-2004-windbg
) installs successfully, so mercifully it looks like it won't be necessary to install different SDK versions under different versions of Windows. I've updated the Dockerfile to use the new Chocolatey package in commit 55eaf4c. Once I've performed tests across various versions of Windows and the Unreal Engine to confirm that there are no incompatible configurations then I'll tag a release with the changes.
That's awesome. Thanks for your work on this!
Can anybody clarify what the work-around is? Yesterday I just did a pip install ue4-docker
so I have the latest version, but sounds like I do not have the fix. When I do a ue4-docker build 4.25.3 --no-engine
I get the download error from the original post. Maybe is there a way to apply the fix to my locally installed ue4-docker?
Thanks
I just want to demonstrate I do have the latest version:
C:\Python39\Scripts>ue4-docker info
ue4-docker version: 0.0.71 (latest available version is 0.0.71)
Operating system: Windows 10 Enterprise Version 2004 (OS Build 19041.572)
Docker daemon version: 19.03.13
NVIDIA Docker supported: No
Maximum image size: 200GB
Available disk space: 225.6 GiB
Total system memory: 31.91 GiB physical, 36.66 GiB virtual
Number of processors: 6 physical, 12 logical
Yet ue4-docker build still doesn't yield the fix:
[ue4-docker build] Building image "adamrehn/ue4-build-prerequisites:2004"...
...
Step 18/27 : RUN choco install -y windbg && echo. && echo.RUN directive complete. Docker will now commit the filesystem layer to disk. && echo.Note that for large filesystem layers this can take quite some time. && echo.Performing filesystem layer commit... && echo.
---> Running in 067b601916c1
Chocolatey v0.10.15
Installing the following packages:
windbg
By installing you accept licenses for the packages.
Progress: Downloading windbg 10.0.10586.15... 100%
windbg v10.0.10586.15 [Approved] - Likely broken for FOSS users (due to download location changes)
windbg package files install completed. Performing other installation steps.
Attempt to get headers for http://download.microsoft.com/download/6/A/2/6A2ECE81-C934-4E47-91CC-52DA00A65345/Installers/e8bc712abeffd7c9711ee3f55d4aa99b.cab failed.
The remote file either doesn't exist, is unauthorized, or is forbidden for url 'http://download.microsoft.com/download/6/A/2/6A2ECE81-C934-4E47-91CC-52DA00A65345/Installers/e8bc712abeffd7c9711ee3f55d4aa99b.cab'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
Downloading windbg
from 'http://download.microsoft.com/download/6/A/2/6A2ECE81-C934-4E47-91CC-52DA00A65345/Installers/e8bc712abeffd7c9711ee3f55d4aa99b.cab'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'http://download.microsoft.com/download/6/A/2/6A2ECE81-C934-4E47-91CC-52DA00A65345/Installers/e8bc712abeffd7c9711ee3f55d4aa99b.cab'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
This package is likely not broken for licensed users - see https://chocolatey.org/docs/features-private-cdn.
The install of windbg was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\windbg\tools\chocolateyInstall.ps1'.
See log for details.
I mean, I see the fix in master: https://github.com/adamrehn/ue4-docker/blob/master/ue4docker/dockerfiles/ue4-build-prerequisites/windows/Dockerfile#L41
And I see the latest version (0.0.71) was released around the time of this fix: https://pypi.org/project/ue4-docker/#history
Any hints on why this still doesn't work?
That's because the latest release doesn't have that commit in it. You can check by going to the file under the release tag:
That said, if you can find that dockerfile in your install, you likely could change that line to match the one in the master branch. For me it's located at C:\Python38\Lib\site-packages\ue4docker\dockerfiles\ue4-build-prerequisites\windows
but obviously the directory may be different due to python/virtualenv locations. Use python -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())"
to find your lib path.
Brilliant, thank you! Here are the steps I used to get unblocked.
python -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())"
ue4docker\dockerfiles\ue4-build-prerequisites\windows\Dockerfile
from that directory.Thanks!
@adamrehn Can we get an 0.0.72 release with 55eaf4c635e55dcf57bc0c405fd225d1bbef7acd please to close this issue?
Or is there some blocking issue or concern with this change that is holding it back?
Apologies for the delay in getting back to this issue, I've been drowning in work over the past few months and watching in horror as my GitHub backlog steadily balloons to ever greater sizes.
I had been planning on thoroughly testing this change across a range of configurations (Windows version / UE4 version) to ensure it doesn't break anything, but given that Windows builds are completely broken without it, I guess it's better to tag a release now and identify any edge cases later. The fix is now live in ue4-docker version 0.0.72.
Output of the
ue4-docker info
command:The
windbg
choco package is broken (see comments on package and thus I can't build a prereq image.