>lxd
lol who uses that in $CURRENT_YEAR. It thought it was merely a ploy to ease old sysops into jumping on the Containers™ bandwagon without making their heads explode
argo is for deploying automatically onto kubernetes, it's unrelated to jenkins and gitlab, gitlab is unrelated to jenkins technically. you can put all your eggs in on basket with gitlab, or you can keep your CI separate in jenkins. smarter not to consolidate completely into gitlab
It's like jenkins, but fir for when you drank the k8s kool-aid. At my $PREVIOUS_JOB we had Argo CD and Argo Workflows. Argo CD is the part that ensures k8s state you commited to a repo is applied to the cluster and sort of worked for production, but choked on our staging cluster (it had a lot of resources, though). Argo Workflows is the part that implements pipelines and it was a buggy mess and writing & debugging pipelines for it was absolutely miserable. Wouldn't recommend, shit like Drone or whatever would be 100% more sane.
nope, I still do it for money. doesn't change the fact I fricking hate it, and what this entire industry has become in the last decade.
2 months ago
Anonymous
get a cloud/db admin job at a small company where k8s is overkill
2 months ago
Anonymous
I don't do admin work. I hate it as a software developer. all this trash keeps piling up additional abstraction levels and results in bloated dev/test/production environments that are borderline impossible to debug. making software has become a nightmare.
2 months ago
Anonymous
How long have you been in the industry? There was plenty of bullshit before docker/k8s.
2 months ago
Anonymous
I've been around since 2005. back then, it was mostly about desktop apps. everything running locally, one process, easy debugging - good times. in recent years, everyone went saas and moved everything to cloud. so now even fairly low-level C++ devs need to deal with devops/cloud bullshit.
2 months ago
Anonymous
All true, but now companies don't have to worry about scaling and utilization, or pay people to handle on-premise administration. Some of those cost savings go to your salary.
2 months ago
Anonymous
>have ironclad desktop app running immaculately for 20 years >"let's gut it and turn it into a web based saas" >management has no idea about devops >entire development team knows nothing about web frameworks >hire two fresh grad to write 50,000 line vue app that keeps it's entire state in the global store >no CI/CD >no containerization >manual deployments to azure VMs using IIS Express
2 months ago
Anonymous
At least you're not making sequel queries agains the database from the frontend : V
I use rootful docker and it's so comfy
frick rootless
it's piss easy
of course I'm only using it on my home server with zero security
got no idea how it's used in business or enterprise
Docker was made to make things easy. You're literally moronic.
Docker is easy but if take your time to read the manual very carefully (like git). More than likely you have watched tutorials or read just enough to get the hello world image running. No judgement on you because it should be that simple. However, most Dockerfiles I’ve seen in production are shit. You got to think out the layering for reproducible builds and you gotta treat the Dockerfile as just a big posix shell script because that’s how it works. After that the compose file is just configuration that should’ve been done with an actual language but oh well. Docker is better than what came before but you gotta dig into the manual and build lots of stuff to get it working a competent level. Don’t give up.
hello Docker users. How do (You) specific debug, say, Python running in a container?
I know of three methods, but don't like any very much.
1. >create compose.debug.yaml >create a launch.json config >run VSCode debug
this is ok, but something seems off about it. The filesystem you see isn't the filesystem of the container.
2. >devcontainers
you can access the filesystem, but can't do step through debugging
3. >docker compose up >docker shell >flask shell >call functions with print statements
slow and tedious
I had to debug php in docker container, as far as I remember you need to put the necessary confs in the root of the project or in the designated folder and run the container with debug mode enabled, most of the time there is no shortcut, you have to do it because that's how your language behaves.
then if you use vscode you set a .vscode/.debug i dont remeber the name and set the json object with the correct mappings to the necessary port on your machine side of course and the correnct path to the fs [machine]:[container], so basically you're creating a bridge between the vscode and the docker instance, it would be a similar concept to remote debug
Are you unemployed?
In the working man's world, when you're made to develop on MacOS, and develop against old ass libraries, it's not possible to run programs outside a container.
2 months ago
Anonymous
On MacOS you run a VM anyway for Docker. So develop your application normally in your VM and then when it's ready deal with containers.
2 months ago
Anonymous
hm, you're right about the VM, but how do I do step through debugging with that method?
2 months ago
Anonymous
I don't know. But you said python so I'm inclined to tell you to frick off for implying you'd have that problem in the first place with PYTHON.
Otherwise I'm sure VSCode and python IDEs offer VM support.
2 months ago
Anonymous
lowly, unemployed behavior
The same way you would debug code running on your system, just in a VM instead. Vscode's remote connection works great for that, I use it to debug my Linux stuff from windows.
I will look into remote connection debugging. Thank you.
2 months ago
Anonymous
I suggested the remote connection feature implicitly to you and you call me unemployed. I am very much employed, moreso than you, and am now officially telling you to frick off for asking shit questions and being shit.
2 months ago
Anonymous
don't be like that babe
2 months ago
Anonymous
The same way you would debug code running on your system, just in a VM instead. Vscode's remote connection works great for that, I use it to debug my Linux stuff from windows.
Docker is easy but if take your time to read the manual very carefully (like git). More than likely you have watched tutorials or read just enough to get the hello world image running. No judgement on you because it should be that simple. However, most Dockerfiles I’ve seen in production are shit. You got to think out the layering for reproducible builds and you gotta treat the Dockerfile as just a big posix shell script because that’s how it works. After that the compose file is just configuration that should’ve been done with an actual language but oh well. Docker is better than what came before but you gotta dig into the manual and build lots of stuff to get it working a competent level. Don’t give up.
morons say this about literally every CLI tool in existence, and when you ask them what a good CLI tool is, they either reply with nothing or something much worse.
>docker's cli is moronic >docker exec mycontainer -it bash
Yes.
morons say this about literally every CLI tool in existence, and when you ask them what a good CLI tool is, they either reply with nothing or something much worse.
Good tools have sensible defaults. Why do I have to build a wrapper script around every common action like connecting to a container or killing all containers.
>Why do I have to build a wrapper script around every common action like connecting to a container
you don't, moron, why the frick would you make a wrapper script for a single command, you're making no sense at all >or killing all containers.
again, this is a single command, make it an alias, are you really this stupid? yes, you are really this stupid, that's why you're complaining, because you're just fricking dumb
2 months ago
Anonymous
Literally two calls to docker >docker kill $(docker ps -q)
2 months ago
Anonymous
so again can you explain why you have to make a wrapper script and not an alias? like dk or something. why are you complaining about something so stupid and trivial that is your fault?
2 months ago
Anonymous
bash too hard, prease understand
2 months ago
Anonymous
cause aliases are for gays
I've never sucked a dick and I've never written an alias
2 months ago
Anonymous
Just use shell with better history search like fish or zsh, br0 - I've never had to write an alias, because fish's history search just werks everytiem
2 months ago
Anonymous
I utilize the search heavily but tmux always seems to mess that up. Sometimes I realize I only know the first two letters of the command I want to use lel
2 months ago
Anonymous
>cause aliases are for gays
lol you're a moron, typical IQfy idiot, doesn't know how to use linux, too stupid to figure anything about himself. fricking homosexual
2 months ago
Anonymous
I mean they are pretty gay, imagine writing `git shiggydiggy` unironically
2 months ago
Anonymous
that's not an alias you fricktard. also, imagine writing a whole command? lol you're dumb. post salary and nose
It is not too hard depending if you use official images or you have to make your own from scratch then good luck.
Most docker images are linux based, so you need to know bash, how to work with linux file system and learn some dockerfile commands and the docker-compose.
Also many times docker exposes some internal constants that act as aliases to addresses and that might be confusing.
Most people simply copy and fine tune other dockerfiles and bash scripts to fit their projects unless you take some advanced course for docker+linux+bash+ect. then don't worry too much, just look on github if someone has solved your problem
>docker services dies >all your containers go down with it
Heh, nothin' personal, kid.
Use Podman instead, docker gives you a single point of failure and opens the door to privilege escalation attacks since its service runs as root.
>Not that hard to learn >Docker website has good tutorial >Excellent documentation >Chatgpt knows docker inside and out
You aren't even trying. Give me your boss's contact so I can take your job.
Only hard part is like when nginx's docker fails to start, so the docker instance is kill, and you have to play hide and seek to find the correct folder to go and edit the damn config.
It's not and it made my life significantly easier. I don't have to worry about distributions, libraries, library, versions, services, whether required services are running or not in the system. I can write the config once and it just works anywhere I need it to.
docker is stupid easy, which is why it's so popular. however, despite how easy it is to use, docker is hot garbage though, and no I don't mean the idea of containers/containerization in general, I mean docker specifically is utter shite
Mostly because docker hinges on one service running as root, which leads to >heightened vulnerability to privilege escalation attacks >single point of failure, if the docker service process goes down,all your containers go down with it.
Containers are great. My operating system comes as an OCI image. I use an arch container on top to enjoy both up-to-date packages and a stable base system, without having to run things as root.
Docker is simply less secure and reliable. At work, migrating all our production containers from docker to podman was very easy and paid off handsomely for application availability and system security.
have you even bothered doing the minimum research yourself? no, you haven't, here ill paste you a link i found: https://www.upguard.com/blog/docker-vs-lxc
ok but you're brown so it doesn't matter, what about the content of the article. find any problems?
2 months ago
Anonymous
I'm going to stick with the white man's solution, sorry rajesh
2 months ago
Anonymous
the creator of docker is white, you fricking pedo
2 months ago
Anonymous
>the creator of docker is white
And docker is shite. Skin colour is irrelevant. Anyone can make shitty software.
2 months ago
Anonymous
>And docker is shite
nope you're some some dumdass eurohomosexual
2 months ago
Anonymous
Docker is fine, but requiring root privileges is just stupid.
2 months ago
Anonymous
you don't have to use root with docker, why do you keep spreading lies over and over? why do you keep saying it's required, you're lying
2 months ago
Anonymous
>You don't have to use root with docker
Then explain why the official documentation involves running either "sudo dockerd" or "sudo systemctl start docker" to start using it.
https://docs.docker.com/engine/install/
2 months ago
Anonymous
you're the exact type of moron that is par for the course for IQfy, you literally cannot under any circumstance understand how to use a search engine, can you. just admit, you do not under any circumstance understand how to use a search engine to find anything. you fricking idiot, god damn you stupid indians are useless
2 months ago
Anonymous
stop being rude and panicking
2 months ago
Anonymous
not spoon feeding you
2 months ago
Anonymous
here you go anon, goodluck!
https://code.visualstudio.com/docs/containers/troubleshooting#_running-as-a-non-root-user
https://docs.docker.com/engine/security/rootless/
2 months ago
Anonymous
But I'm already using podman, i don't need docker, rootless or not.
2 months ago
Anonymous
what do you put inside your pods, podman?
But where to start learning Docker?
>debugging python and docker 101 >https://code.visualstudio.com/docs/containers/debug-python
I understand it's extremely phaggy to have to write a tasks.json and launch.json file that's basically the same shit as a docker-compose.yaml file, but these files are basically written for you when you generate them.
Docker is an abomination. I have tried time and time again to use it, but every time it just never works for any project I try to use it with.
On the other hand running making a python venv just fricking works and makes it easy to uninstall and find the files and the dependencies.
They're not hard, you know it, this is a strawman where you pretend not to understand that people don't want all of their daily use software to be a separate virtual machine
>debugging python and docker 101 >https://code.visualstudio.com/docs/containers/debug-python
I understand it's extremely phaggy to have to write a tasks.json and launch.json file that's basically the same shit as a docker-compose.yaml file, but these files are basically written for you when you generate them.
because it's a shitty solution to the deployment complex that creates more problems than it solves
i pity those that have to use it because their company thinks they can cheap out on infra not realizing that they will still need the admins only that now they make them use shitty corporate bloatware that has to serve a myriad of use- and edgecases and meet other marketability requirements like automagic quick start procedures that frick everything up for actual professionals whose aspiration goes beyond "i don't exactly know how but i got it running so shut up and give me my money"
Absolute cope
Containers is when devs take your job by coding the infrastructure around their application so they don't have to explain to you how to run it.
Nomad is pretty okay for self-hosting. The downside is that it doesn't have such a big community like k8s does (and as such sometimes annoying corner-cases, like subvolumes on CSI volumes not working properly). But is considerably simpler than k8s, while not requiring you to manually wrangle each node like you'd have to do plain docker-compose.
Skill issue. Git gud son.
use lxd or incus instead, docker is user hostile
>use buzzword, docker is buzzword
sigh............
>lxd
lol who uses that in $CURRENT_YEAR. It thought it was merely a ploy to ease old sysops into jumping on the Containers™ bandwagon without making their heads explode
I run docker in LXC, works quite nicely
blocks you're path
kubernetes truly is a b***h. cluster? more like clusterfrick
Can't hate. The Openshift Kubernetes cluster + ArgoCD + Jenkins + Gitlab + Podman stack at work is the one on-prem infrastructure that actually works.
why jenkins if you already got gitlab
>ArgoCD
What does it so that Jenkins or Gitlab Runner can't do?
Why use ArgoCD? I am genuinely curious.
argo is for deploying automatically onto kubernetes, it's unrelated to jenkins and gitlab, gitlab is unrelated to jenkins technically. you can put all your eggs in on basket with gitlab, or you can keep your CI separate in jenkins. smarter not to consolidate completely into gitlab
It's like jenkins, but fir for when you drank the k8s kool-aid. At my $PREVIOUS_JOB we had Argo CD and Argo Workflows. Argo CD is the part that ensures k8s state you commited to a repo is applied to the cluster and sort of worked for production, but choked on our staging cluster (it had a lot of resources, though). Argo Workflows is the part that implements pipelines and it was a buggy mess and writing & debugging pipelines for it was absolutely miserable. Wouldn't recommend, shit like Drone or whatever would be 100% more sane.
this. frick docker. frick k8s. frick ~~*devops*~~. frick ~~*cloud*~~.
filtered. more jobs and money for me
nope, I still do it for money. doesn't change the fact I fricking hate it, and what this entire industry has become in the last decade.
get a cloud/db admin job at a small company where k8s is overkill
I don't do admin work. I hate it as a software developer. all this trash keeps piling up additional abstraction levels and results in bloated dev/test/production environments that are borderline impossible to debug. making software has become a nightmare.
How long have you been in the industry? There was plenty of bullshit before docker/k8s.
I've been around since 2005. back then, it was mostly about desktop apps. everything running locally, one process, easy debugging - good times. in recent years, everyone went saas and moved everything to cloud. so now even fairly low-level C++ devs need to deal with devops/cloud bullshit.
All true, but now companies don't have to worry about scaling and utilization, or pay people to handle on-premise administration. Some of those cost savings go to your salary.
>have ironclad desktop app running immaculately for 20 years
>"let's gut it and turn it into a web based saas"
>management has no idea about devops
>entire development team knows nothing about web frameworks
>hire two fresh grad to write 50,000 line vue app that keeps it's entire state in the global store
>no CI/CD
>no containerization
>manual deployments to azure VMs using IIS Express
At least you're not making sequel queries agains the database from the frontend : V
I'm not tech savvy at all and docker was piss easy. You might have a genuine mental moronation anon
hello Docker users. How do (You) specific debug, say, Python running in a container?
I know of three methods, but don't like any very much.
1.
>create compose.debug.yaml
>create a launch.json config
>run VSCode debug
this is ok, but something seems off about it. The filesystem you see isn't the filesystem of the container.
2.
>devcontainers
you can access the filesystem, but can't do step through debugging
3.
>docker compose up
>docker shell
>flask shell
>call functions with print statements
slow and tedious
I had to debug php in docker container, as far as I remember you need to put the necessary confs in the root of the project or in the designated folder and run the container with debug mode enabled, most of the time there is no shortcut, you have to do it because that's how your language behaves.
then if you use vscode you set a .vscode/.debug i dont remeber the name and set the json object with the correct mappings to the necessary port on your machine side of course and the correnct path to the fs [machine]:[container], so basically you're creating a bridge between the vscode and the docker instance, it would be a similar concept to remote debug
run a remote debugger inside the container and connect to it from vscode. It may require host.docker.internal hostname setting
Why would you need to do that? Debug your application normally outside a container if it has bugs. That's not the point of containers.
Are you unemployed?
In the working man's world, when you're made to develop on MacOS, and develop against old ass libraries, it's not possible to run programs outside a container.
On MacOS you run a VM anyway for Docker. So develop your application normally in your VM and then when it's ready deal with containers.
hm, you're right about the VM, but how do I do step through debugging with that method?
I don't know. But you said python so I'm inclined to tell you to frick off for implying you'd have that problem in the first place with PYTHON.
Otherwise I'm sure VSCode and python IDEs offer VM support.
lowly, unemployed behavior
I will look into remote connection debugging. Thank you.
I suggested the remote connection feature implicitly to you and you call me unemployed. I am very much employed, moreso than you, and am now officially telling you to frick off for asking shit questions and being shit.
don't be like that babe
The same way you would debug code running on your system, just in a VM instead. Vscode's remote connection works great for that, I use it to debug my Linux stuff from windows.
it's piss easy
of course I'm only using it on my home server with zero security
got no idea how it's used in business or enterprise
Which server OS?
Linux
I use rootful docker and it's so comfy
frick rootless
>filtered by yaml
Docker is easy but if take your time to read the manual very carefully (like git). More than likely you have watched tutorials or read just enough to get the hello world image running. No judgement on you because it should be that simple. However, most Dockerfiles I’ve seen in production are shit. You got to think out the layering for reproducible builds and you gotta treat the Dockerfile as just a big posix shell script because that’s how it works. After that the compose file is just configuration that should’ve been done with an actual language but oh well. Docker is better than what came before but you gotta dig into the manual and build lots of stuff to get it working a competent level. Don’t give up.
Docker was made to make things easy. You're literally moronic.
then it needs to be easier...
please tell us how, you can't
how exactly, you won't say
docker's cli is moronic
It's perfectly fine, and competent users write their own bash scripts around the cli anyway
>It's perfectly fine
>users write their own bash scripts around the cli
lol, lmao even
Indian detected
morons say this about literally every CLI tool in existence, and when you ask them what a good CLI tool is, they either reply with nothing or something much worse.
compare lxd/incus cli to docker
>docker's cli is moronic
>docker exec mycontainer -it bash
Yes.
Good tools have sensible defaults. Why do I have to build a wrapper script around every common action like connecting to a container or killing all containers.
>Why do I have to build a wrapper script around every common action like connecting to a container
you don't, moron, why the frick would you make a wrapper script for a single command, you're making no sense at all
>or killing all containers.
again, this is a single command, make it an alias, are you really this stupid? yes, you are really this stupid, that's why you're complaining, because you're just fricking dumb
Literally two calls to docker
>docker kill $(docker ps -q)
so again can you explain why you have to make a wrapper script and not an alias? like dk or something. why are you complaining about something so stupid and trivial that is your fault?
bash too hard, prease understand
cause aliases are for gays
I've never sucked a dick and I've never written an alias
Just use shell with better history search like fish or zsh, br0 - I've never had to write an alias, because fish's history search just werks everytiem
I utilize the search heavily but tmux always seems to mess that up. Sometimes I realize I only know the first two letters of the command I want to use lel
>cause aliases are for gays
lol you're a moron, typical IQfy idiot, doesn't know how to use linux, too stupid to figure anything about himself. fricking homosexual
I mean they are pretty gay, imagine writing `git shiggydiggy` unironically
that's not an alias you fricktard. also, imagine writing a whole command? lol you're dumb. post salary and nose
It is not too hard depending if you use official images or you have to make your own from scratch then good luck.
Most docker images are linux based, so you need to know bash, how to work with linux file system and learn some dockerfile commands and the docker-compose.
Also many times docker exposes some internal constants that act as aliases to addresses and that might be confusing.
Most people simply copy and fine tune other dockerfiles and bash scripts to fit their projects unless you take some advanced course for docker+linux+bash+ect. then don't worry too much, just look on github if someone has solved your problem
>docker services dies
>all your containers go down with it
Heh, nothin' personal, kid.
Use Podman instead, docker gives you a single point of failure and opens the door to privilege escalation attacks since its service runs as root.
>Not that hard to learn
>Docker website has good tutorial
>Excellent documentation
>Chatgpt knows docker inside and out
You aren't even trying. Give me your boss's contact so I can take your job.
>Why are dockers so damn hard bros
docker compose
Only hard part is like when nginx's docker fails to start, so the docker instance is kill, and you have to play hide and seek to find the correct folder to go and edit the damn config.
t. docker noob
>create container
>pull image and run
> exists after 10 seconds
Logs say something about host
wrong
It's not and it made my life significantly easier. I don't have to worry about distributions, libraries, library, versions, services, whether required services are running or not in the system. I can write the config once and it just works anywhere I need it to.
>dockers
indian detected
docker is stupid easy, which is why it's so popular. however, despite how easy it is to use, docker is hot garbage though, and no I don't mean the idea of containers/containerization in general, I mean docker specifically is utter shite
why
Mostly because docker hinges on one service running as root, which leads to
>heightened vulnerability to privilege escalation attacks
>single point of failure, if the docker service process goes down,all your containers go down with it.
Containers are great. My operating system comes as an OCI image. I use an arch container on top to enjoy both up-to-date packages and a stable base system, without having to run things as root.
Docker is simply less secure and reliable. At work, migrating all our production containers from docker to podman was very easy and paid off handsomely for application availability and system security.
Why don't use guys like lxc
have you even bothered doing the minimum research yourself? no, you haven't, here ill paste you a link i found: https://www.upguard.com/blog/docker-vs-lxc
can you read at least? or no?
The author looks brown
ok but you're brown so it doesn't matter, what about the content of the article. find any problems?
I'm going to stick with the white man's solution, sorry rajesh
the creator of docker is white, you fricking pedo
>the creator of docker is white
And docker is shite. Skin colour is irrelevant. Anyone can make shitty software.
>And docker is shite
nope you're some some dumdass eurohomosexual
Docker is fine, but requiring root privileges is just stupid.
you don't have to use root with docker, why do you keep spreading lies over and over? why do you keep saying it's required, you're lying
>You don't have to use root with docker
Then explain why the official documentation involves running either "sudo dockerd" or "sudo systemctl start docker" to start using it.
https://docs.docker.com/engine/install/
you're the exact type of moron that is par for the course for IQfy, you literally cannot under any circumstance understand how to use a search engine, can you. just admit, you do not under any circumstance understand how to use a search engine to find anything. you fricking idiot, god damn you stupid indians are useless
stop being rude and panicking
not spoon feeding you
here you go anon, goodluck!
https://code.visualstudio.com/docs/containers/troubleshooting#_running-as-a-non-root-user
https://docs.docker.com/engine/security/rootless/
But I'm already using podman, i don't need docker, rootless or not.
what do you put inside your pods, podman?
What the frick is even that?
Docker is an abomination. I have tried time and time again to use it, but every time it just never works for any project I try to use it with.
On the other hand running making a python venv just fricking works and makes it easy to uninstall and find the files and the dependencies.
Just steer clear off the bridge, saar
They're not hard, you know it, this is a strawman where you pretend not to understand that people don't want all of their daily use software to be a separate virtual machine
the thinking man's choice
>thinking man
>no one uses it
>meme wrapper
yeah really does make you think, doesn't it
>thinking man
>no one uses it
QED
It's pretty gud. Wish podman compose + buildah had full docker compose parity though.
>put two or more services in the same pod
>access all of them with just 1 IP
so comfy for selfhosting
These dolphins are much cuter than the docker whale, that’s it I’m switching to podman
itt dumbasses who can't google or use the command line. bunch of dumb windows babies
Because instead of coding you spend all your time playing with your wienerer
>debugging python and docker 101
>https://code.visualstudio.com/docs/containers/debug-python
I understand it's extremely phaggy to have to write a tasks.json and launch.json file that's basically the same shit as a docker-compose.yaml file, but these files are basically written for you when you generate them.
I love the challenge of working with it
But where to start learning Docker?
^
^_^
Just don't use it, simple as.
because it's a shitty solution to the deployment complex that creates more problems than it solves
i pity those that have to use it because their company thinks they can cheap out on infra not realizing that they will still need the admins only that now they make them use shitty corporate bloatware that has to serve a myriad of use- and edgecases and meet other marketability requirements like automagic quick start procedures that frick everything up for actual professionals whose aspiration goes beyond "i don't exactly know how but i got it running so shut up and give me my money"
OK, what's the alternative when you have thousands of machines with innumerable permutations for hardware components?
Absolute cope
Containers is when devs take your job by coding the infrastructure around their application so they don't have to explain to you how to run it.
while not the most user friendly out there dockers aren't exactly a rocket science either. sounds like a (you) problem.
Docker (and Docker Compose) is a godsend for selfhosting.
K8s is nice but overkill for selfhosting.
Nomad is pretty okay for self-hosting. The downside is that it doesn't have such a big community like k8s does (and as such sometimes annoying corner-cases, like subvolumes on CSI volumes not working properly). But is considerably simpler than k8s, while not requiring you to manually wrangle each node like you'd have to do plain docker-compose.
how do I run sql server in docker without it absolutely destroying the memory usage of my machine
>sql server
There's your problem.