[BUG] [2026-07-03T11:24:53.415+0800] ERR utils.cc:145 Couldn't read '/config/queue.json': No such file or directory (2) (utils.cc:145)

Open
#325 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start at utils.cc:145 and inspect the container configuration and logs around the missing /config/queue.json path. Reproduce the report using the provided Docker context, determine the expected behavior for that file, and verify the issue is resolved without introducing a new startup error.

Written by the indexing model from the issue text.

Description

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

[2026-07-03T11:24:53.415+0800] ERR utils.cc:145 Couldn't read '/config/queue.json': No such file or directory (2) (utils.cc:145)

Expected Behavior

[2026-07-03T11:24:53.415+0800] ERR utils.cc:145 Couldn't read '/config/queue.json': No such file or directory (2) (utils.cc:145)

Steps To Reproduce

[2026-07-03T11:24:53.415+0800] ERR utils.cc:145 Couldn't read '/config/queue.json': No such file or directory (2) (utils.cc:145)

Environment
[2026-07-03T11:24:53.415+0800] ERR utils.cc:145 Couldn't read '/config/queue.json': No such file or directory (2) (utils.cc:145)
CPU architecture

x86-64

Docker creation
[2026-07-03T11:24:53.415+0800] ERR utils.cc:145 Couldn't read '/config/queue.json': No such file or directory (2) (utils.cc:145)
Container logs
[2026-07-03T11:24:53.415+0800] ERR utils.cc:145 Couldn't read '/config/queue.json': No such file or directory (2) (utils.cc:145)
Dominant language
Dockerfile
Stars
739
Forks
205
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.

More from linuxserver/docker-transmission

All issues in linuxserver/docker-transmission

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.