tailscale-dev / tailscale-dev/ScaleTail
🐞 Bug: Immich service failing database connection
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 124
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 4
Description
Bug Description
All the containers in the Immich stack come up except for the main one: app-${SERVICE}-server, it's failing with:
[app-immich-server] 2026-05-24T22:02:47.442325026Z Node.js v24.14.1
[app-immich-server] 2026-05-24T22:03:38.741846578Z Initializing Immich v2.7.5
[app-immich-server] 2026-05-24T22:03:38.747900514Z Detected CPU Cores: 16
[app-immich-server] 2026-05-24T22:03:39.933416295Z (node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
[app-immich-server] 2026-05-24T22:03:39.933449882Z (Use `node --trace-warnings ...` to show where the warning was created)
[app-immich-server] 2026-05-24T22:03:39.960166499Z node:internal/process/promises:394
[app-immich-server] 2026-05-24T22:03:39.960184263Z triggerUncaughtException(err, true /* fromPromise */);
[app-immich-server] 2026-05-24T22:03:39.960186134Z ^
[app-immich-server] 2026-05-24T22:03:39.960187644Z
[app-immich-server] 2026-05-24T22:03:39.960189100Z Error: getaddrinfo ENOTFOUND database
[app-immich-server] 2026-05-24T22:03:39.960190662Z at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {
[app-immich-server] 2026-05-24T22:03:39.960192251Z errno: -3008,
[app-immich-server] 2026-05-24T22:03:39.960193747Z code: 'ENOTFOUND',
[app-immich-server] 2026-05-24T22:03:39.960195219Z syscall: 'getaddrinfo',
[app-immich-server] 2026-05-24T22:03:39.960196666Z hostname: 'database'
[app-immich-server] 2026-05-24T22:03:39.960198149Z }
[app-immich-server] 2026-05-24T22:03:39.960199559Z
[app-immich-server] 2026-05-24T22:03:39.960200972Z Node.js v24.14.1
[app-immich-server] 2026-05-24T22:04:40.083079285Z Initializing Immich v2.7.5
[app-immich-server] 2026-05-24T22:04:40.089008410Z Detected CPU Cores: 16
[app-immich-server] 2026-05-24T22:04:41.262146145Z (node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
[app-immich-server] 2026-05-24T22:04:41.262162803Z (Use `node --trace-warnings ...` to show where the warning was created)
[app-immich-server] 2026-05-24T22:04:41.287359013Z node:internal/process/promises:394
[app-immich-server] 2026-05-24T22:04:41.287370773Z triggerUncaughtException(err, true /* fromPromise */);
[app-immich-server] 2026-05-24T22:04:41.287373656Z ^
[app-immich-server] 2026-05-24T22:04:41.287375344Z
[app-immich-server] 2026-05-24T22:04:41.287376912Z Error: getaddrinfo ENOTFOUND database
[app-immich-server] 2026-05-24T22:04:41.287383778Z at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {
[app-immich-server] 2026-05-24T22:04:41.287385468Z errno: -3008,
[app-immich-server] 2026-05-24T22:04:41.287396842Z code: 'ENOTFOUND',
[app-immich-server] 2026-05-24T22:04:41.287398436Z syscall: 'getaddrinfo',
[app-immich-server] 2026-05-24T22:04:41.287399993Z hostname: 'database'
[app-immich-server] 2026-05-24T22:04:41.287401587Z }
Can't figure it out. Is it because database isn't in the same network?
Expected Behavior
A running container
Actual Behavior
Failing with
Error: getaddrinfo ENOTFOUND database
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'database'
}
Screenshots
No response
Operating System
Linux
Tailscale Version
latest
Docker Version
29.4.2
Relevant Logs or Error Messages
Docker Compose Configuration
Environment Configuration (.env file)
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Docker Compose Configuration and environment configuration for app-${SERVICE}-server, the database service, and their networks. Reproduce the startup failure and inspect the service names and network membership; done means the server resolves database and remains running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, node.js
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100