# FMOD errors during startup using Epic's Docker container image

**URL:** <https://qa.fmod.com/t/fmod-errors-during-startup-using-epics-docker-container-image/20554>\
**Category:** Unreal Engine\
**Created:** [August 16, 2023, 8:58pm UTC](https://qa.fmod.com/t/fmod-errors-during-startup-using-epics-docker-container-image/20554 "2023-08-16T20:58:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AOOSG](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@AOOSG](https://qa.fmod.com/u/AOOSG)\
**Post date:** [August 16, 2023, 8:58pm UTC](https://qa.fmod.com/t/fmod-errors-during-startup-using-epics-docker-container-image/20554/1 "2023-08-16T20:58:34Z")

</div>

Hi, I was hoping someone was able to help me get FMOD running inside Epic’s [docker container image](https://github.com/orgs/EpicGames/packages/container/unreal-engine/28865577?tag=runtime-windows-ltsc2022). The docker image does not have an audio system service running which seems to be a problem.

Here’s the errors we’re having on startup:

1. I got a COM error which I fixed by applying [this](https://github.com/fmod/fmod-for-unreal/pull/68) PR, please consider accepting it!
2. I have an error I don’t know how to fix, it’s the same as is described [here](https://qa.fmod.com/t/multiple-errors-running-unreal-engine-plugin-in-docker-containers/17966)

```auto
LogInit: Display: LogFMOD: Error: c:\jk\workspace\Build __2.2__ Unreal_Win\core_api\platforms\win\src\fmod_os_misc.cpp(100) - IMMDeviceEnumerator::RegisterEndpointNotificationCallback returned 0x80070424.
LogInit: Display: LogFMOD: Error: 'FMOD::Studio::System::create(&StudioSystem)' returned 'Error initializing output device.'
LogInit: Display: LogFMOD: Error: 'StudioSystem->getCoreSystem(&lowLevelSystem)' returned 'An invalid object handle was used.'
LogInit: Display: LogFMOD: Error: 'lowLevelSystem->setOutput(FMOD_OUTPUTTYPE_NOSOUND_NRT)' returned 'An invalid object handle was used.'
LogInit: Display: LogFMOD: Error: 'StudioSystem->initialize(1, FMOD_STUDIO_INIT_ALLOW_MISSING_PLUGINS | FMOD_STUDIO_INIT_SYNCHRONOUS_UPDATE, FMOD_INIT_MIX_FROM_UPDATE, nullptr)' returned 'An invalid object handle was used.'
LogInit: Display: Failure - 5 error(s), 0 warning(s)

```

Any thoughts on how I can fix this would be appreciated!

A couple of things I’ve tried:

1. Inside the container: `net start audiosrv` → “The service name is invalid.”
2. Inside the container: `net start "Windows Audio"` → The service name is invalid.
3. Return early from `FFMODStudioModule::LoadLibraries()` → Crashes later in the startup when trying to load banks?
4. The build system already passes `-nosound`, `-buildmachine` etc. to UE5 on startup.

According to [this](https://unrealcontainers.com/docs/concepts/audio-output) website UE5’s audio system does not have this issue because it uses an XAudio2 null audio device, perhaps FMOD could do the same?

The container is based on Epic’s `ghcr.io/epicgames/unreal-engine:runtime-windows-ltsc2022` which is `Windows Server 2022 (21H2) [10.0.22621.825]`.

`systeminfo` output:

```auto
OS Name: Microsoft Windows Server 2022 Datacenter
OS Version: 10.0.22621 N/A Build 22621
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Server

```

---

<div class="post-metadata">

**Author:** ![AOOSG](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@AOOSG](https://qa.fmod.com/u/AOOSG)\
**Post date:** [August 21, 2023, 10:42pm UTC](https://qa.fmod.com/t/fmod-errors-during-startup-using-epics-docker-container-image/20554/2 "2023-08-21T22:42:23Z")

</div>

I fixed this by building my own image based on `server` rather than relying on Epic’s image (that uses `servercore`). Not ideal because of the additional maintenance burden, and having to use a more bloated image, but it fixes the issue.

---

<div class="post-metadata">

**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\
**Post date:** [June 14, 2024, 12:44am UTC](https://qa.fmod.com/t/fmod-errors-during-startup-using-epics-docker-container-image/20554/3 "2024-06-14T00:44:03Z")

</div>

We have a fix for this in the upcoming release 2.02.23.