Skip to content

Container downloads Server Package on every restart #11

Description

@phil-lipp

Hi there,

during setup of my Hytale server today I had to go back and forth a bit and what really bothered me during that process was that the Container redownloaded the Server Package on each startup, thus also triggering the double authentication prompt each time. This is of course kinda redundant as there were no updates to the package during that time and also causes unnecessary load on the download servers.

From what I can gather looking at this repo, it seems to stem from the recommended docker-compose.yaml (pasted below for reference) not containing the full "/hytale" directory but instead dedicated mounts for the separate subfolders. Since the relevant server files ("HytaleServer.jar" etc) and the VERSION file, which is used to determine the current installed version and would thus lead to skipping the download, are inside /hytale but outside the dedicated mountpoints from the compose file, they don't persist.

services:
    hytale:
        image: ghcr.io/machinastudios/hytale
        stdin_open: true
        tty: true
        ports:
            - "5520:5520/udp"
        volumes:
            - ./backups:/hytale/backups
            - ./mods:/hytale/mods
            - ./logs:/hytale/logs
            - ./universe:/hytale/universe
        environment:
            - SERVER_ACCEPT_EARLY_PLUGINS=true
            - SERVER_BIND=0.0.0.0:5520
            - SERVER_BACKUP_DIR=/hytale/backups
            - SERVER_BACKUP_INTERVAL=10
            - SERVER_MAX_VIEW_RADIUS=12

Would it be feasible restructure the /hytale directory and add dedicated mountpoints for the server files (e.g. /hytale/server) as well as the config files (e.g. /hytale/configs)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions