117
How many containers are you all running? (lemmy.world)
submitted 6 months ago by to c/selfhosted@lemmy.world
146 comments fedilink hide all child comments
 

There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.

But now I am curious, what are your counts? I would guess those of you running k*s would win out by pod scaling

docker ps | wc -l

For those wanting a quick count.

you are viewing a single comment's thread
view the rest of the comments
[–] 16 points 6 months ago (6 children)

All of you bragging about 100+ containers, please may in inquire as to what the fuck that's about? What are you doing with all of those?

  • permalink
  • fedilink
  • source
  • hideshow 12 child comments
    •
  • [–] 7 points 6 months ago (2 children)

    In my case, most things that I didn't explicitly make public are running on Tailscale using their own Tailscale containers.

    Doing it this way each one gets their own address and I don't have to worry about port numbers. I can just type http://cars/ (Yes, I know. Not secure. Not worried about it) and get to my LubeLogger instance. But it also means I have 20ish copies of just the Tailscale container running.

    On top of that, many services, like Nextcloud, are broken up into multiple containers. I think Nextcloud-aio alone has something like 5 or 6 containers it spins up, in addition to the master container. Tends to inflate the container numbers.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [+] 0 points 6 months ago (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 months ago

    Possibly. I don't remember that being an option when I was setting things up last time.

    From what I'm reading it's sounding like it's just acting as a slightly simplified DNS server/reverse proxy for individual services on the tailnet. Sounds Interesting. I'm not sure it's something I'd want to use on the backend (what happens if Tailscale goes down? Does that DNS go down too?), but for family members I've set up on the tailnet, it sounds like an interesting option.

    Much as I like Tailscale, it seems like using this may introduce a few too many failure points that rely on a single provider. Especially one that isn't charging me anything for what they provide.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 6 months ago* (last edited 6 months ago) (1 child)

    A little of this, a little of that...I may also have a problem... >_>;

    The ListQuickstart

    • dockersocket
    • ddns-updater
    • duckdns
    • swag
    • omada-controller
    • netdata
    • vaultwarden
    • GluetunVPN
    • crowdsec

    Databases

    • postgresql14
    • postgresql16
    • postgresql17
    • Influxdb
    • redis
    • Valkey
    • mariadb
    • nextcloud
    • Ntfy
    • PostgreSQL_Immich
    • postgresql17-postgis
    • victoria-metrics
    • prometheus
    • MySQL
    • meilisearch

    Database Admin

    • pgadmin4
    • adminer
    • Chronograf
    • RedisInsight
    • mongo-express
    • WhoDB
    • dbgate
    • ChartDB
    • CloudBeaver

    Database Exporters

    • prometheus-qbittorrent-exporter
    • prometheus-immich-exporter
    • prometheus-postgres-exporter
    • Scraparr

    Networking Admin

    • heimdall
    • Dozzle
    • Glances
    • it-tools
    • OpenSpeedTest-HTML5
    • Docker-WebUI
    • web-check
    • networking-toolbox

    Legally Acquired Media Display

    • plex
    • jellyfin
    • tautulli
    • Jellystat
    • ErsatzTV
    • posterr
    • jellyplex-watched
    • jfa-go
    • medialytics
    • PlexAniSync
    • Ampcast
    • freshrss
    • Jellyfin-Newsletter
    • Movie-Roulette

    Education

    • binhex-qbittorrentvpn
    • flaresolverr
    • binhex-prowlarr
    • sonarr
    • radarr
    • jellyseerr
    • bazarr
    • qbit_manage
    • autobrr
    • cleanuparr
    • unpackerr
    • binhex-bitmagnet
    • omegabrr

    Books

    • BookLore
    • calibre
    • Storyteller

    Storage

    • LubeLogger
    • immich
    • Manyfold
    • Firefly-III
    • Firefly-III-Data-Importer
    • OpenProject
    • Grocy

    Archival Storage

    • Forgejo
    • docmost
    • wikijs
    • ArchiveTeam-Warrior
    • archivebox
    • ipfs-kubo
    • kiwix-serve
    • Linkwarden

    Backups

    • Duplicacy
    • pgbackweb
    • db-backup
    • bitwarden-export
    • UnraidConfigGuardian
    • Thunderbird
    • Open-Archiver
    • mail-archiver
    • luckyBackup

    Monitoring

    • healthchecks
    • UptimeKuma
    • smokeping
    • beszel-agent
    • beszel

    Metrics

    • Unraid-API
    • HDDTemp
    • telegraf
    • Varken
    • nut-influxdb-exporter
    • DiskSpeed
    • scrutiny
    • Grafana
    • SpeedFlux

    Cameras

    • amcrest2mqtt
    • frigate
    • double-take
    • shinobipro

    HomeAuto

    • wyoming-piper
    • wyoming-whisper
    • apprise-api
    • photon
    • Dawarich
    • Dawarich---Sidekiq

    Specific Tasks

    • QDirStat
    • alternatrr
    • gaps
    • binhex-krusader
    • wrapperr

    Other

    • Dockwatch
    • Foundry
    • RickRoll
    • Hypermind

    Plus a few more that I redacted.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 6 months ago (2 children)

    I look at this list and cry a little bit inside. I can't imagine having to maintain all of this as a hobby.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 6 months ago

    Kube makes it easy to have a lot, as a lot of things you need to deploy on every node just deploy on every node. As odd as it sounds, the number of containers provides redundancy that makes the hobby easy. If a Zimaboard dies or messes up, I just nuke it, and I don't care whats on it.

  • permalink
  • fedilink
  • source
  • parent