this post was submitted on 09 Feb 2026
36 points (97.4% liked)

Selfhosted

60911 readers
1138 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
 

Ive got a lot of downloaded YouTube videos. I used to play them through Plex back when I ran that, but once I switched to Jellyfin there wasn't a good way to set them up at all. So I was super excited when I found TubeArchivist. All the posts I saw on it seemed to be positive, so I set it up yesterday in Docker.

It seemed to work alright at first, but it took a really long time for the server to start up once I started running the containers. I'm also running Navisphere, Jellyfin, Kiwix, and a Tor snowflake node, which all booted up instantly, but this took 5-10 minutes to be accessible. It also took like twice the Docker resources of all my other containers just to run.

Doing anything in it was super slow too. Logging in was unresponsive, took a couple minutes to load. There was no feedback either so I thought it was just frozen. I had all my videos I had downloaded previously, so I tried importing them and that just brought my system to a complete crawl. It maxed out Dockers allocated resources, even exceeding the CPU allocation. It also caused Docker to crash twice.

Does anyone have any experience with this program? Did I do something wrong in my docker-compose file (I just modified the example in the github repository) or is the program just super poorly optimized? I've been able to run all the other containers on my system just fine. It has a lot of the same functionality as Jellyfin, which does not do this kind of crap. I was so excited but its been a huge letdown. Any thoughts?

you are viewing a single comment's thread
view the rest of the comments
[–] Shimitar@downonthestreet.eu 4 points 5 months ago* (last edited 5 months ago) (2 children)

I run TA with success since many months. It's fast and responsive, so I guess it's an issue with your setup?

The metadata bridge to jellyfin alfo works pretty nice, I have no complaints...

You can check my notes at https://wiki.gardiol.org/doku.php?id=services%3Atubearchivist

But be advised I am on rootless podman with docker compose

[–] ToTheGraveMyLove@sh.itjust.works 2 points 5 months ago

I'll take a look at that when I get home, thank you. That gives me hope. I thought I was going to have to abandon it with how awful it was running. Fingers crossed.

[–] ToTheGraveMyLove@sh.itjust.works 1 points 5 months ago (1 children)

Okay, your notes have definitely helped a bit. I compared your compose file against mine and removed the HOST_UID, HOST_GID, and the healthcheck sections from the default file. Its still taking an abnormal amount of time to boot up and login, but the container isn't completely throttling my system anymore. I suspect the healthcheck was the culprit. A step in the right direction though, thank you!

[–] Shimitar@downonthestreet.eu 1 points 5 months ago

I removed health checks because o think they don't work properly with podman how I use it, but I might be wrong.

Anyway, glad it helped! That's the spirit why I wrote it.