this post was submitted on 27 Aug 2023
11 points (92.3% liked)

Selfhosted

60588 readers
1658 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
11
Invidious Docker install hanging? (discuss.tchncs.de)
submitted 2 years ago by Karcinogen@discuss.tchncs.de to c/selfhosted@lemmy.world
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?

you are viewing a single comment's thread
view the rest of the comments
[–] CumBroth@discuss.tchncs.de 6 points 2 years ago* (last edited 2 years 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.

[–] Karcinogen@discuss.tchncs.de 4 points 2 years ago

That was my issue. Thank you very much!

[–] WhyAUsername_1@lemmy.world 2 points 2 years ago* (last edited 2 years 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 @CumBroth@discuss.tchncs.de says

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

It should be

    ports:
      - "3000:3000"
[–] CumBroth@discuss.tchncs.de 3 points 2 years 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

[–] Karcinogen@discuss.tchncs.de 2 points 2 years ago

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