Does this still work? Issue creating bind mount / persistent storage for game files

[mikesellt]

No matter what I've tried so far, the image doesn't create any folders or files. I have several other docker images running via compose, and they all create files and folders. I don't see this one actually create anything, and the logs show file not found errors. Any help?

Thanks

[misel228]

It's running perfectly fine on my machine with the provided docker-compose.yml.

A few more pieces of information might be helpful. e.g. the logs that show the file not found errors.

[mikesellt]

Thanks for your reply! I think the problem is happening since I'm trying to use a persistent mount to a specific folder instead of just using a docker volume like the compose file has by default. Here are my logs (I think the most recent is at the top and the beginning is at the bottom):

ut99-server-1 | [D] System/User.ini
ut99-server-1 | [D] System/ucc-bin
ut99-server-1 | Traceback (most recent call last):
ut99-server-1 | File "/prepare.py", line 331, in
ut99-server-1 | [D] System/UnrealTournament.ini
ut99-server-1 | [D] System/wx-ut-bin
ut99-server-1 | [D] System/ut-bin
ut99-server-1 | main()
ut99-server-1 | File "/prepare.py", line 18, in main
ut99-server-1 | prepare()
ut99-server-1 | File "/prepare.py", line 154, in prepare
ut99-server-1 | for entry in os.listdir(folderPath):
ut99-server-1 | ^^^^^^^^^^^^^^^^^^^^^^
ut99-server-1 | FileNotFoundError: [Errno 2] No such file or directory: '/ut-data/Maps'
ut99-server-1 | WARNING: Not using preference directory
ut99-server-1 | WARNING: Using system ini file: /ut-server/System/UnrealTournament.ini
ut99-server-1 | WARNING: Using user ini file: /ut-server/System/User.ini
ut99-server-1 | Executing Class Engine.ServerCommandlet
ut99-server-1 | Unreal engine initialized
ut99-server-1 | Browse: CTF-Face?Name=Player?Class=Botpack.TMale2?team=255?skin=SoldierSkins.blkt?Face=SoldierSkins.Othello?game=BotPack.CTFGame?mutator=BotPack.SniperArena,MapVoteLAv2.BDBMapVote,FlagAnnouncementsV2.FlagAnnouncements,ZeroPingPlus103.ZP_SniperArena,KickIdlePlayers2.KickIdlePlayers2
ut99-server-1 | LoadMap: CTF-Face?Name=Player?Class=Botpack.TMale2?team=255?skin=SoldierSkins.blkt?Face=SoldierSkins.Othello?game=BotPack.CTFGame?mutator=BotPack.SniperArena,MapVoteLAv2.BDBMapVote,FlagAnnouncementsV2.FlagAnnouncements,ZeroPingPlus103.ZP_SniperArena,KickIdlePlayers2.KickIdlePlayers2
ut99-server-1 | Bound to Fire.so
ut99-server-1 | Bound to IpDrv.so
ut99-server-1 | Collecting garbage
ut99-server-1 | Purging garbage
ut99-server-1 | Garbage: objects: 17597->17597; refs: 229185
ut99-server-1 | Game class is 'CTFGame'
ut99-server-1 | Sockets: Socket queue 262144 / 262144
ut99-server-1 | Sockets: I am 3be25ffdb460 (172.17.0.2)
ut99-server-1 | TcpNetDriver on port 7777
ut99-server-1 | Server Package: SoldierSkins
ut99-server-1 | Server Package: CommandoSkins
ut99-server-1 | Server Package: FCommandoSkins
ut99-server-1 | Server Package: SGirlSkins
ut99-server-1 | Server Package: BossSkins
ut99-server-1 | Server Package: Botpack
ut99-server-1 | Server Package: MultiMesh
ut99-server-1 | Server Package: Relics
ut99-server-1 | Server Package: EpicCustomModels
ut99-server-1 | Server Package: TCowMeshSkins
ut99-server-1 | Server Package: TNaliMeshSkins
ut99-server-1 | Server Package: TSkMSkins
ut99-server-1 | Server Package: De
ut99-server-1 | MD5 protection enabled: FALSE
ut99-server-1 | Spawning: IpDrv.UdpBeacon
ut99-server-1 | Spawning: IpServer.UdpServerQuery
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: IpServer.UdpServerUplink
ut99-server-1 | Spawning: UWeb.WebServer
ut99-server-1 | Bound to UWeb.so
ut99-server-1 | Fixing up CTF-Face boulders
ut99-server-1 | Bringing Level CTF-Face.MyLevel up for play (50)...
ut99-server-1 | InitGame: ?Name=Player?Class=Botpack.TMale2?team=255?skin=SoldierSkins.blkt?Face=SoldierSkins.Othello?game=BotPack.CTFGame?mutator=BotPack.SniperArena,MapVoteLAv2.BDBMapVote,FlagAnnouncementsV2.FlagAnnouncements,ZeroPingPlus103.ZP_SniperArena,KickIdlePlayers2.KickIdlePlayers2
ut99-server-1 | Base Mutator is CTF-Face.DMMutator0
ut99-server-1 | Mutators BotPack.SniperArena,MapVoteLAv2.BDBMapVote,FlagAnnouncementsV2.FlagAnnouncements,ZeroPingPlus103.ZP_SniperArena,KickIdlePlayers2.KickIdlePlayers2
ut99-server-1 | Add mutator BotPack.SniperArena
ut99-server-1 | Add mutator MapVoteLAv2.BDBMapVote
ut99-server-1 | Failed to load MapVoteLAv2: Can't find file for package MapVoteLAv2..
ut99-server-1 | Failed to load "Class MapVoteLAv2.BDBMapVote": Can't find file for package MapVoteLAv2..
ut99-server-1 | Add mutator FlagAnnouncementsV2.FlagAnnouncements
ut99-server-1 | Failed to load FlagAnnouncementsV2: Can't find file for package FlagAnnouncementsV2..
ut99-server-1 | Failed to load "Class FlagAnnouncementsV2.FlagAnnouncements": Can't find file for package FlagAnnouncementsV2..
ut99-server-1 | Add mutator ZeroPingPlus103.ZP_SniperArena
ut99-server-1 | Failed to load ZeroPingPlus103: Can't find file for package ZeroPingPlus103..
ut99-server-1 | Failed to load "Class ZeroPingPlus103.ZP_SniperArena": Can't find file for package ZeroPingPlus103..
ut99-server-1 | Add mutator KickIdlePlayers2.KickIdlePlayers2
ut99-server-1 | Failed to load KickIdlePlayers2: Can't find file for package KickIdlePlayers2..
ut99-server-1 | Failed to load "Class KickIdlePlayers2.KickIdlePlayers2": Can't find file for package KickIdlePlayers2..
ut99-server-1 | UdpServerQuery(crt): Port 7778 successfully bound.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | DoUplink is not set. Not connecting to Master Server.
ut99-server-1 | Webserver is not enabled. Set bEnabled to True in Advanced Options.
ut99-server-1 | Initiating local logging...
ut99-server-1 | Initiating world logging...
ut99-server-1 | Game engine initialized

[mikesellt]

I have two servers I'm trying to use, and I'm getting a similar result with each. One is a Synology NAS using Container Manager, but it's basically a frontend for Docker compose. And the other is a linux server running CasaOS frontend, which again, is just basically a gui for Docker compose. Neither has been able to create folders or files. I'm probably missing something obvious, but I do have several other containers on each system using persistent storage instead of Docker volumes.

[mikesellt]

If it helps, here's the docker compose I'm using on the Synology:

services:
ut99-server:
image: roemer/ut99-server:latest
volumes:
- ./ut99data:/ut-data
ports:
# Webadmin
- 5580:5580
# Game Play
- '7777:7777'
# Server Querying
- '7778:7778'
- '7779:7779'
- '7780:7780'
- '7781:7781'
# LAN Discovery
- '8777:8777'
# Server Announcement
- '27500:27500'
- '27900:27900'
environment:
PGID: 1000
PUID: 1000
UT_SERVERURL: "CTF-Face?game=BotPack.CTFGame?mutator=BotPack.InstaGibDM,MVES.MapVote,FlagAnnouncementsV2.FlagAnnouncements"
UT_SERVERNAME: "My UT Server"
UT_ADMINNAME: UTAdmin
UT_ADMINEMAIL: no@one.com
UT_MOTD1: "Have Fun"
UT_ADMINPWD: admin
UT_WEBADMINUSER: admin
UT_WEBADMINPWD: admin
UT_MINPLAYERS_DM: 4
UT_MINPLAYERS_CTF: 8
UT_MAXPLAYERS: 32
UT_INITIALBOTS_DM: 4
UT_INITIALBOTS_CTF: 8

the only things I really changed from the default compose file is removing the version, changing the volume, and adding the user and group environment variables (I thought it may have been a permissions issue).

[Roemer]

I don't really remember why, but it needs to be a volume. Why can't you use one? You can even create a bind volume to place it wherever you want and declare it external in compose.

[Firehawke]

Edit: Nevermind. I just saw the section of text I'd missed saying bind mounts won't work.

Seems like the best solution is to actually grab the dockerfile and everything else and build it locally if you want to make any adjustments to the overall package.

[shalak]

In order to have all the bells and whistles created by author, you need named volumes, because this docker does not populate the /ut-data in runtime, but in build time. It's a direct consequence of those parts of Dockerfile:

# Additional Mutators
ADD files/Mutators/* /ut-data/
# Additional Mods
ADD files/Mods/* /ut-data/
# Additional Maps Packed
ADD files/Maps-Packed/* /ut-data/
# Customized Configs
ADD files/Configs/* /ut-data/System/
# Additional Single Maps
ADD files/Maps/* /ut-data/Maps/

If you create a bind volume, it will be empty, and container does not have logic of populating it - only image has.

All you'd need is to fork this, and make it ADD somewhere else and make the /startup.sh move them to /ut-data - that would solve the issue. I think you could hack it up even without forking - start once with named volume, copy all the contents to host and then start again with bind mount to the place you copied it (but I'm not sure how it would affect the later VOLUME /ut-data call)

As of now, I personally do not see this as a big issue, as I don't plan adding new mods on daily basis, and simple docker cp can copy files into the named volume anyway. But nevetheless it's a design limitation that could be solved like I described above with negligible performance impact.