Horde Server - Out of Date Image on GitHub

Hello,

In the process with upgrading to 5.6, we are looking at deploying a Horde Server for our organization.

We wanted to use the pre-built image from GitHub, but it appears to be out of date (4 months old).

Any reason for this ? Is it possible to have it updated ?

Thanks!

Steps to Reproduce

  1. In Epic’s GitHub Releases for HordeServer:
    1. https://github.com/orgs/EpicGames/packages/container/package/horde\-server
  2. Notice that HordeServer image was published 4 months ago
    1. Out of synced with 5.6 that just released

Hey there Jonathan,

We are in the process of generating the release image.

Julian

Hey there Jeremy,

Ah yes, so what you’re encountering here is a dependency that we have (on docker) to generate the dashboard application for Horde (built in React). If you install docker on your windows machine, you should be able to complete the MSI installer (which contains the dashboard application).

Related for the original post, you should be able to build your own docker image of the 5.6 Horde server via:

  1. RunUAT.bat BuildGraph -Script=Engine/Source/Programs/Horde/BuildHorde.xml -Target=“Build Bundled Docker Image”

Julian

Sorry to interject, but I’m trying to build Horde myself from source via

RunUAT.bat BuildGraph -Script=Engine/Source/Programs/Horde/BuildHorde.xml -Target=“Build Horde Server Installer”

Seems to largely be working, but it doesn’t quite finish.

It dies here. I don’t have docker on my windows box, and when I look in the BuildHorde.xml, the Stage Horde Installer Dashboard seems to be a linux thing?

Is this necessary to build the windows installer?

`****** [10/13] Stage Horde Installer Dashboard

Writing text to file ‘D:\p4\7thcurse\devtest\Staging\Dashboard\index.html’: placeholder
Building Docker image
Copying 280 file(s) using max 64 thread(s)
BUILD FAILED: Couldn’t find the executable to run: docker
while executing task
at D:\p4\7thcurse\devtest\Engine\Source\Programs\Horde\BuildHorde.xml(250)
(see D:\p4\7thcurse\devtest\Engine\Programs\AutomationTool\Saved\Logs\Log.txt for full exception trace)
AutomationTool executed for 0h 1m 20s
AutomationTool exiting with ExitCode=1 (Error_Unknown)`