Selfhosted

60177 readers

574 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How do you manage you DB in a docker environment? (sh.itjust.works)

submitted 1 week ago by Croquette@sh.itjust.works to c/selfhosted@lemmy.world

34 comments fedilink hide all child comments

Hello,

As the title suggests, how do you manage your DBs for docker services.

Do you spin a new DB for every new docker cluster or do you have a centralized DB that is accessible to the docker clusters.

What are the pros and cons of both method?

For the moment, I spin a new DB for every services as I feel it is easier to backup the service in case of a problem.

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

[–] IratePirate@feddit.org 2 points 1 week ago* (last edited 1 week ago) (2 children)

//Edit: terminology improvements

One per service. Not just because it's easy, but because it allows you to minimise blast radius. If you're running one ~~DB~~ DBMS per ~~container~~ service and one container gets compromised, only that one ~~DB~~ DBMS is compromised. With one centralised ~~DB~~ DBMS for all containers, a breach of one container means access to the data of all containers that use this without the need for any lateral movement.

[–] placebo@lemmy.zip 1 points 1 week ago

a breach of one container means access to the data of all containers

How so? Each service uses its own database with credentials that provide access only to that database. Unless on top of a breach in your container there is some zero-day in your DBMS - which I find highly improbable - no other data will be affected.

[–] Viceversa@lemmy.world 1 points 1 week ago (1 children)

Now, is it one DB per container
Or one DBMS+DM per container?

[–] IratePirate@feddit.org 2 points 1 week ago* (last edited 1 week ago)

Apologies for being imprecise on terminology. I meant the latter, per service.