[BUG] Web-UI is accessible much later after starting the container compared to previous versions

Open
#75 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
docker, docker-compose

Research direction

Start with the provided docker compose configuration and container logs, then compare startup behavior between 4.4.x and 4.5.0-ls223 using the Windows NTFS bind-mounted /config volume. Investigate what occurs after "[ls.io-init] done." and verify that the web UI becomes accessible promptly after the change.

Written by the indexing model from the issue text.

Description

no-issue-activity
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

In 4.5.0-ls223, it takes a few minutes for webui to be accessible after "[ls.io-init] done." is shown in the docker terminal.
It's almost immediately accessible after starting the container in 4.4.x versions.

Expected Behavior

No response

Steps To Reproduce

In Docker Windows x64, spin up a container with "docker compose up -d". There's data carried from container on previous version and the volume is directly mapped to directories in NTFS partition.

Environment
- OS: Windows 11 x64
- How docker service was installed: winget
CPU architecture

x86-64

Docker creation
services:
  thelounge:
    image: lscr.io/linuxserver/thelounge:latest
    container_name: thelounge
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=${TZ}
    volumes:
      - ./:/config
    ports:
      - 9000:9000
    restart: unless-stopped
Container logs
[migrations] started

[migrations] no migrations found

usermod: no changes

───────────────────────────────────────


      ██╗     ███████╗██╗ ██████╗

      ██║     ██╔════╝██║██╔═══██╗

      ██║     ███████╗██║██║   ██║

      ██║     ╚════██║██║██║   ██║

      ███████╗███████║██║╚██████╔╝

      ╚══════╝╚══════╝╚═╝ ╚═════╝


   Brought to you by linuxserver.io

───────────────────────────────────────


To support LSIO projects visit:

https://www.linuxserver.io/donate/


───────────────────────────────────────

GID/UID

───────────────────────────────────────


User UID:    1000

User GID:    1000

───────────────────────────────────────

Linuxserver.io version: v4.5.0-ls223

Build-date: 2026-05-20T06:35:52+00:00

───────────────────────────────────────

    

[custom-init] No custom files found, skipping...

2026-05-22 06:07:54 [WARN] /config/logs is world readable. The log files may be exposed. Please fix the permissions.

2026-05-22 06:07:54 [WARN] run `chmod o-x "/config/logs"` to correct it.

2026-05-22 06:07:55 [INFO] The Lounge v4.5.0 (Node.js 22.22.2 on linux x64)

2026-05-22 06:07:55 [INFO] Configuration file: /config/config.js

(node:147) ExperimentalWarning: SQLite is an experimental feature and might change at any time

(Use `node --trace-warnings ...` to show where the warning was created)

2026-05-22 06:07:55 [INFO] Available at http://[::]:9000/ in private mode

2026-05-22 06:07:55 [WARN] /config/vapid.json is world readable. The file contains secrets. Please fix the permissions.

2026-05-22 06:07:55 [WARN] run `chmod o= "/config/vapid.json"` to correct it.

2026-05-22 06:07:55 [INFO] User XXX loaded

Connection to localhost (::1) 9000 port [tcp/*] succeeded!

[ls.io-init] done.
Dominant language
Dockerfile
Stars
36
Forks
13
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.