Selfhosted

39250 readers

259 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Invidious Docker install hanging? (discuss.tchncs.de)

submitted 1 year ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

I'm trying to setup an invidious instance with Docker, but it isn't completing.

invidious_1 | 2023-08-27 17:23:46 UTC [info] 200 GET /api/v1/comments/jNQXAC9IVRw 479.27ms

It's been giving the same message for over an hour, and I can't connect to the web interface either. Any ideas?

top 5 comments

sorted by: hot top controversial new old

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (2 children)

That log entry is unrelated to whatever issues you're having. That's what the default docker-compose.yaml uses for health checks:

  healthcheck:
      test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/comments/jNQXAC9IVRw || exit 1
      interval: 30s
      timeout: 5s
      retries: 2

The fact that it returns a 200 probably means that Invidious is properly up and running. Could you elaborate further on what you mean by "setup isn't completing"? How are you trying to connect to the web UI? Sharing your docker-compose.yaml might help us debug as well.

Edit: I just noticed that the default compose file has the port bound to localhost:

    ports:
      - "127.0.0.1:3000:3000"

which means you won't be able to access it from other machines inside or outside your network. You'd have to change that to - "3000:3000" to enable access for other machines.

[–] [email protected] 4 points 1 year ago

That was my issue. Thank you very much!

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (2 children)

To add to this, are you running docker-compose up with a -d flag?

When I got into Dockers, I got confused when the docker command would not complete (i.e. get back to bash shell after completing the command). In docker, you need to specify the "-d" flag to run it in background (i.e. separate daemon)

One more point, when @[email protected] says

You'd need to change that to 3000:3000.

It should be

    ports:
      - "3000:3000"

[–] [email protected] 3 points 1 year ago

Ooooh, good catch. I assumed "it's been giving me the same message for over an hour" to mean that they've been monitoring the logs, not running in interactive mode. O_O

[–] [email protected] 2 points 1 year ago

Thank You! I changed the port settings and used the "d" flag and it's working.