Selfhosted

40219 readers

1052 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Is dockStarter a waste of time? (lemmy.ml)

submitted 5 months ago* (last edited 5 months ago) by Mountain_Mike_420@lemmy.ml to c/selfhosted@lemmy.world

29 comments fedilink hide all child comments

Should I be learning docker compose instead of relying on dockStarter to manage my containers? I got portainer up, should I just use that to manage my stack?

I’m committed this summer to finally learning docker. I’m on day 3 and the last puzzle piece is being able to access qbittorrent locally while running the container through the vpn.

you are viewing a single comment's thread
view the rest of the comments

[–] mhzawadi@lemmy.horwood.cloud 6 points 5 months ago (1 children)

What you need then is swarm compose, that can run any service in global mode (in all nodes all the time) or scale mode.

[–] just_another_person@lemmy.world 5 points 5 months ago (1 children)

No, then you're just orchestrating the service level stuff, and nothing else. Docker's tools will never compare to cluster scaling efforts where the entire horizontal layer to be scaled can be orchestrated from the instance up to containers.

[–] mhzawadi@lemmy.horwood.cloud 1 points 5 months ago (1 children)

not sure I understand you, in docker swarm your containers are started on n number of works from a single compose file on a manager. you can add any number of work nodes to scale your service as needed

[–] just_another_person@lemmy.world 2 points 5 months ago* (last edited 5 months ago) (1 children)

N number of EXISTING nodes. Proper container orchestration platforms handle all the provisioning of instances, scaling of services, IAM...etc.

Docker Swarm (and all Docker tools) only handle...Docker.

Swarm is another thing I would never recommend in production.

[–] mhzawadi@lemmy.horwood.cloud 0 points 5 months ago (1 children)

That's not container orchestration, that's infrastructure orchestration. Depending on your use case docker swarm could just the right tool for the job.

You've been using Aws and they will happily let you add more nodes to your container runner of choice

[–] just_another_person@lemmy.world 1 points 5 months ago

No, it's container orchestration. As-in "I orchestrate all the scaling needed to run and scale the containers".