Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

immich_server container makes request to registry.npmjs.org every 30 seconds #10796

Closed
1 of 3 tasks
justinhorton opened this issue Jul 3, 2024 · 4 comments · Fixed by #10811
Closed
1 of 3 tasks

immich_server container makes request to registry.npmjs.org every 30 seconds #10796

justinhorton opened this issue Jul 3, 2024 · 4 comments · Fixed by #10811

Comments

@justinhorton
Copy link

The bug

This may be working as designed, but I'm not familiar enough with NodeJS apps to say. I noticed in my pi-hole logs that registry.npmjs.org had become a top hit and traced it back to the immich_server container. When I first set up immich and its firewall rules earlier this year, I wasn't seeing any traffic to the public internet after the models were downloaded, which is consistent with what Alex said here:

"Everything should work offline after the models get downloaded and the reverse geocoding files get downloaded"

Can you confirm whether this frequency of requests to the NPM registry is intended?

The OS that Immich Server is running on

debian 12 bookworm

Version of Immich Server

v1.106.4

Version of Immich Mobile App

N/A

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

same as the release docker-compose.yml

Your .env content

standard

Reproduction steps

Start the immich stack and see DNS requests to registry.npmjs.org every 30 seconds, accompanied by HTTPS connections to one of the registry.npmjs.org IPs.

Relevant log output

No response

Additional information

No response

@mertalev
Copy link
Contributor

mertalev commented Jul 3, 2024

I'm not aware of a reason it should be making requests to npmjs.org, let alone every 30 seconds. Others can chime in if this is a known / expected behavior.

@bo0tzz
Copy link
Member

bo0tzz commented Jul 3, 2024

Just to double check - you're using exactly the official docker compose stack, with the latest container images from ghcr.io?

@mmomjian
Copy link
Contributor

mmomjian commented Jul 3, 2024

Can you please add the following to the immich_server docker compose container, then run docker compose up -d?

healthcheck:
  disable: true

@justinhorton
Copy link
Author

Can you please add the following to the immich_server docker compose container, then run docker compose up -d?

healthcheck:
  disable: true

This is the culprit. The requests stop with the immich_server healthcheck (added in #9583) disabled. It appears that npm run itself causes a hit to registry.npmjs.org. I tested this inside the immich_server container and saw the same outbound request with npm run or npm run healthcheck.

Aaaand I see that y'all fixed this while I was typing this response. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants