1. i'm using docker
2. i don't use "the cures"
3. nobody "suppresses" ftp
you're retarded
1. i'm using docker
2. i don't use "the cures"
3. nobody "suppresses" ftp
you're retarded
also...docker isn't a file-transfer-protocol...it's using cgroups and nNamespaces to isolate processes.
im running a proxmox server with 2 virtual machines (pfsense and docker).
my docker vm hosts these services:
openldap
nextcloud
peertube 1
peertube 2
mastodon
hedgedoc
gogs
excalidraw
elk_cluster
searx
lightning network daemon (testnet)
lightning network daemon (mainnet)
bitcoin fullnode
bitcoin mempool stats
wordpress
mailcow emailserver
@mk @theorytoe you missed the point. containers just make things harder. they are nice rube goldberg machines for shit languages like python which are hell to deploy.
when just installing everything from packages, things will receive timely security patches of the distribution.
when using VMs, one has to upgrade a few VMs for this. not great, not terrible.
with containers one has to hope that some image down the stack will be upgraded to include the fix, while the whole setup provides worse isolation than VMs (which already is prone to leakage). with containers the isolation is essentially the same as for plain linux users and chroot. no improvement. cgroups limiting resource usage can be set by the init system, i think systemd does this already.
containers sure have their use case, but mostly they are a crappy solution waiting for problems.
in the end the image is a meme which makes the point that ftp-ing a directory full of php scripts worked better than all the modern shit.
your solution is to..what?
run everything in their own VM? -> ressource nightmare
run everything on one host (without container)? -> security nightmare
bro..you're retarded.
"vms can use dynamic allocation for years now."
if you're running 16 vms, you're also running 16 kernel, right? and you'd have to do 16 operating system upgrades, right?
aka .. ressource nightmare
@mk @theorytoe
- vms can use dynamic allocation for years now.
- containers provide absolutely no additional security.
running on the host is perfectly fine. it only requires one to know what one is doing, of course.
lastly, i'd be careful to calling other people retard when using "bro".
"containers provide absolutely no additional security"
then it would be pretty easy for you to proof your statement? i'm waiting.
"lastly, i'd be careful to calling other people retard when using "bro"."
fuck you, faggot.
stop talking, start linking
@mk @theorytoe
pretty easy, they can't be more safe than the technologies they are composed of. in practice they are more insecure because of the bullshit update mechanisms.
"in practice they are more insecure because of the bullshit update mechanisms."
your argument is bullshit.
90% of the webservices i run do maintain their own Dockerfile and/or docker images on hub.docker.com
peertube updated their development images 3hours ago.
"Last pushed 3 hours ago"
https://hub.docker.com/r/chocobozzz/peertube/tags
---
peertube uses the latest official debian image. they get updates as soon as new versions release.
"16 containers have to be updated as well"
we're talking infrastructure update here...you'd also have to run your retarded ftp-php-update scripts also 16 times.
@mk @theorytoe if running 16 kernels eats all your ram, you have other problems. 16 containers have to be updated as well. with a sane diatribution i have security updates in around one day 💁
@RGBCube @theorytoe @bonifartius
you guys are pretty good at talking and pretty shitty at linking to your sources.
@mk @bonifartius @theorytoe Systemd does everything already, look at a random NixOS module that configures it.
I've had it with these docker faggots
dann gibt mir die deutschen versionen
@mk @theorytoe sorry, the relevant articles aren't available in simple english :)
@mk @theorytoe @bonifartius https://github.com/NixOS/nixpkgs/blob/master/nixos%2Fmodules%2Fservices%2Fsecurity%2Fendlessh.nix#L42-L96
Or look at literally ANY file under nixos/services/
@RGBCube @theorytoe @bonifartius
the position you're defeding is this:
"containers provide absolutely no additional security"
please provide evidence for this claim.
@mk @theorytoe @bonifartius Systemd already has cgroups, choosing and protecting kernel modules and anything related to the kernel. You don't need d*cker, as systemd already has EVERYTHING. And you optionally give access to specific ports so it can function properly.
Depends on what you mean containerization, but systemd already does it, ignoring the port usage.
@RGBCube @theorytoe @bonifartius
ok..to make it even simpler for you..
- there's a webservice running.
- it gets hacked.
- the hacker owns the webservice (the process)
is it harder or easier for the attacker to own the host system if..
scenario 1: process is isolated from the host system via cgroups and namespaces.
scenario 2: process is NOT isolated from the host system via cgroups and namespaces.
@RGBCube @theorytoe @bonifartius
bro...nobody is talking about your faggot systemd..
this is the position you retards took:
"containers provide absolutely no additional security"
please defend it or lose this debate.
@mk @theorytoe @bonifartius Systemd is also scenario 1, if you do it properly. Which is done here
@mk @RGBCube @theorytoe
i have to do some drywall now, so i'll keep it short:
- namespaces are a copy of a plan9 idea to have composable environments, isolation is a side effect.
- cgroups limit resource usage, might be worthwhile to prevent some daemon going crazy. otoh there already were things in place for that like umask.
- chroot is no "container feature". postfix chroots by default, so do many other daemons. you still need good user/group structure and appropriately set permissions in any case.
all of these things are usable without resorting to docker. @RGBCube explained how a distribution can use the same features with it's packages.
side note: you using words like "retard" and "faggot" while shilling docker which frequently has pride events borders on the comedic.
@bonifartius @RGBCube @theorytoe
are these two technologies making a operating system saver from a hijacked/hacked process?
yes or no.
- namespaces are a copy of a plan9 idea to have composable environments, isolation is a side effect.
- cgroups limit resource usage, might be worthwhile to prevent some daemon going crazy. otoh there already were things in place for that like umask.
to make it short, because you'll never admit it anyway..
yes they do.
so you lost this position:
"containers provide absolutely no additional security"
@bonifartius @RGBCube @theorytoe
"docker which frequently has pride events borders on the comedic."
what's you position?
i should stop using docker, because there're activists working on it?
---
well...how about you stop using the linux kernel then.
@bonifartius @RGBCube @theorytoe
"made up facts"
i quoted you. i used you as a fact.
don't be mad. you'll win next time.
@mk @RGBCube @theorytoe
> unilaterally declares victory due to made up facts
bless your heart
i described pretty well what the things involved do and what they were made for. @RGBCube explained that they are in use by distribution packages.
i can't keep you from using fluoridated stuff like docker or proxmox. maybe it's one of these things in life one has to learn the hard way :blobcatshrug:
@RGBCube @theorytoe @bonifartius
i migrated my stuff around already. it's easy, because i've got very few dependencies.
proxmox -> home example
1. rent a little vm with public ipv4-address
2. import pfsense backup-file
3. start vpn from home to pfsense
4. stopp all docker container on old machine
5. move data
6. start docker container
proxmox desaster recovery (german):
https://hedgedoc.satoshishop.de/kS1jwalbQOWzW5hvxLd6_Q#
@RGBCube @theorytoe @bonifartius
proxmox uses kvm/qemu and zfs (zvols)
migrate to physical machine:
1. put new harddrive (/dev/sdb) into proxmox server
2. copy data to /dev/sdb
$ dd if=/dev/zvol/rpool/data/vm-101-disk-0 of=/dev/sdb bs=1GB
$ cfdisk /dev/sdb # resize disk
$ e2fsck -f /dev/sdb-part3 # check
$ resize2fs /dev/sdb-part3 # resize part.
3. put /dev/sdb into new machine 4. boot from it
name one other hypervisor that allow you to do this.
@RGBCube @theorytoe @bonifartius
proxmox (desaster recovery from backup) -> proxmox:
https://hedgedoc.satoshishop.de/kS1jwalbQOWzW5hvxLd6_Q#
tldr:
1. install new one
2. copy VM-config files
3. recreate the linux-bridges from the old /etc/network/interfaces
4. zfs send all the zvols
5. start virtual machines
@RGBCube @theorytoe @bonifartius
you can convert your zvols very easy into every format you might need with "qemu-img convert"
types:
- RAW (zvol)
- QCOW2
- VMDK
- VDI
- VHDX
https://cloudbase.it/qemu-img-windows/
---
$ qemu-img convert -f raw /dev/zvol/pool/vm-311-disk-0 -O vdi vm-311-disk-0.vdi
@RGBCube @theorytoe @bonifartius
Migrating a complete IT environment (proxmox) from one location to another in less than 10min
@bonifartius @RGBCube @theorytoe
it's ok. you're allowed to be a faggot.
@mk @RGBCube @theorytoe i don't have to stop using anything as i'm not the one, according to the insults used by you, who has a problem with what people are :)
@bonifartius @RGBCube @theorytoe
ok.. and while we wait for your doomsday prediction, the whole world moves to containerization.
..the whole world? no !
a little man in germany is fighting back by putting all his php-egg into one basket.
@mk @RGBCube @theorytoe it's ok, just think of me when your jenga software stack breaks :)
@bonifartius @RGBCube @theorytoe
jupp.
your all-eggs-one-basket-system is far superior.
@mk @RGBCube @theorytoe and who always wins in your cultural reference?
@Moon @theorytoe @mk haven't used lxc in a long time, i think since they switched to using images? is it worth the trouble?
"containers are a solution to a self-inflicted problem being that people dont want to actually write software that is runable bare-metal"
what does "running containers" have to do with bare-metal? you can run containers within a bare-metal system. it doesn't make sense.
"containers provide no security"
if it's so unsecure, why did none of you like me reallife examples of hacked processes breaking out of docker containers? please provide evidence for your statements.
"docker works fine for prebuilt images, but..."
just use the Dockerfile the devs provide.
and build your docker image with them
$ lnd_version=v0.17.3-beta.rc1
$ apt install git
$ git clone https://github.com/lightningnetwork/lnd /tmp/lnd && cd /tmp/lnd
$ docker build . --build-arg checkout=$lnd_version -t lnd:$lnd_version
use your new docker-image (lnd:v0.17.3-beta.rc1) by replacing it in the docker-compose.yml (see video)
https://mastodon.satoshishop.de/@mk/111819231243916351
"docker[..]load balancing[..]nighmare"
nobody in this thread ever talked about load balancing. this thread is mainly about docker-isolation/security.
"if you cant run software bare-metal without hassle its not good software"
if you've got bad software, would you rather run in inside or outside a container?
the argument is that docker/containers in general don't have to run within a virtual machine.
@theorytoe @bonifartius
Containers use the kernel of the host system and create an illusionary environment..
chroot
- changes the current root directory
unshare - creates namespaces for:
- User
- Process ID (PID)
- Network
- Mount
- Interprocess Communication (IPC)
..in which the process is allowed to run wild without being able to break anything on the host. there is no kernel abstraction.
*edit like -> LINK
is your argument that docker is too complex?
complex in what sense?
docker doesn't use any virtual devices. it basically just changes directories / pointers somewhere else.
it's still "bare-metal", you fucking retard.
"It has no real benefits"
please answer the question:
"if you've got bad software, would you rather run in inside or outside a container?"
is your argument that docker is too complex? -> "In every sense?"
installing software is part of too complex in "every sense", correct?
ok..here's a 10min video that enables noobs to install a bitcoin lightning network daemon that reachable from the internet without the need of:
- a static ip
- a public ip
- a domain name
- a ssl certificate
- portforwarding in the router
- firewall rule in the router
https://mastodon.satoshishop.de/@mk/111819231243916351
docker makes it god damn easy.
in this senacrio you have to, because your customer is forcing you to do it.
i don't believe you.
your customer doesn't want to run 16 VMs, because it's too expensive.
https://mastodon.satoshishop.de/@mk/111843926971242212
https://mastodon.satoshishop.de/@mk/111844044661439465
we already went through this argument. it's a ressource (and management btw) nightmare.
counter question.
what's got more adoption?
installing shit via docker or bash-scripts?
customer: please run these webapps
- nextcloud
- peertube 1
- peertube 2
- mastodon
- hedgedoc
- gogs
- excalidraw
- elk_cluster
- searx
- lightning network daemon (testnet)
- lightning network daemon (mainnet)
- bitcoin fullnode
- bitcoin mempool stats
- wordpress
- mailcow emailserver
please run these services for me.
you: we'll run 16 operating systems and you gotta pay me for pushing software updates to every one of those.
customer: too expensive
i'm using 13 opensource webapps.
https://mastodon.satoshishop.de/@mk/111848148348012587
11 of them have dockerfiles right in their official repo.
https://github.com/nextcloud/docker/blob/59dd41aaca14d3cd3ddbf072973c1b8a7bc14cc8/Dockerfile-debian.template#L4
https://github.com/Chocobozzz/PeerTube/blob/88006beeb379d55b4448da73b4063863295b36dc/support/docker/production/Dockerfile.bookworm#L4
https://github.com/mastodon/mastodon/blob/main/Dockerfile
https://github.com/hedgedoc/hedgedoc/blob/17aade09347e7dd54218a71693690e206c7c821f/frontend/docker/Dockerfile#L4
https://github.com/gogs/gogs/blob/7b06bf642a04f3ee5485da185c53d990df062a12/Dockerfile#L4
https://github.com/excalidraw/excalidraw/blob/d426cc968d49071749c0d831490501cf572eb571/Dockerfile#L4
https://github.com/elastic/elasticsearch/blob/4c4463305630010e1d362b867bf83033b1e63d6e/distribution/docker/src/docker/Dockerfile#L4
https://github.com/searx/searx/blob/276ffd3f01cdd823f75676c51231fad4040059d3/Dockerfile#L2
https://github.com/lightningnetwork/lnd/blob/cf4f468ab5c70e644d8974145d1ffd74a3dabc35/Dockerfile#L4
https://github.com/mempool/mempool-cli/blob/fdb8d4002ff34f82ab210f4eafa3ca3ee2d7ba70/Dockerfile#L4
https://github.com/search?q=org%3Amailcow%20dockerfile&type=code
show me the ansible files in their repos.
"or just run 16 processes on the host machine"
without containerization?
"You understand THAT A VM HOSTS MORE THAN ONE SERVICE."
and if you don't isolate them, one hacked webapp is going take over EVERYTHING !
the argument tldr..
you: docker too complex
me: complex?
you: everything!
me: install easy
you: MANUAL INSTALL !
me: no adoption. devs support docker ! <3
"You seems to want to prove my point more :mel_laugh:"
how?
I am team one basket with process isolation (containers)..from the start.
YOU seem to switch teams a lot...
"run it in a vm"
https://annihilation.social/objects/72331913-a20c-4303-ab62-12872b91608d
"You understand THAT A VM HOSTS MORE THAN ONE SERVICE."
https://annihilation.social/objects/31ce2e17-11fb-4bb4-b0dd-82e48dde942a
"or just run 16 processes on the host machine"
without containerization?
your answer: yes
---
so you're team one basked (no process isolatin)
great !
"SHIPPING CONTAINERS dont help with security"
no. you guys just said it a lot..
---
i repeatetly asked for evidence and you didn't provide me anything.
"if it's so unsecure, why did none of you LINK me reallife-examples of hacked processes breaking out of docker containers?"
https://mastodon.satoshishop.de/@mk/111847966227810935
"you guys are pretty good at talking and pretty shitty at linking to your sources."
https://mastodon.satoshishop.de/@mk/111844129068587581
stop talking, start linking
https://mastodon.satoshishop.de/@mk/111844103725119686
"smart enough to know what docker is they probably should manage it themselves"
because docker is easy to use, right?
"we were talking about having one rouge app"
nobody in this thread was talking about a "rouge-app". we talked about webapps/processes getting hacked in general. we didn't specify how it's getting hacked.
"You really like to make very obvious misinterpretation, your worse than a bad actor you know your part in the script."
i like to use reason and logic to make positions and arguments.
you guys are pretty shitty debaters though.
"you have a full ass search engine"
why would i make an argument for you? it's your job.
---
#5 [..] Anyone who claims something has to provide the evidence for it. Everything you research for the other side can, in case of doubt, simply be parried with "I never said that / never linked it"
"if OpenBSD[..]dislikes docker"
well. i'm not a sheep. i'd like to make up my own mind.
"bad software"
i did mean software that's got unpatched security vurnerabilities.
what's your definition of "rogue app"?
"sweep contrary evidence aside..."
you guys never provided any evidence. that's the problem.
you guys make claims and ignore me when i'm asking for proof.
@theorytoe@ak.kyaruc.moe @mk@mastodon.satoshishop.de @dcc@annihilation.social @bonifartius@qoto.org don't even need vulnerabilities to point to, docker is the sort of thing that sounds neat in theory, but in practice ends up being nothing more than a fuckton of complexity for complexity's sake.
It's the pinnacle of the worst kind of developer behavior. The kind so high on their farts, they think that other developers should have to put up with their bullshit simply because they're developers.
Which seems to be a pretty good description of the guy you're arguing with lol
@dotnet @theorytoe @dcc @bonifartius
"don't even need vulnerabilities"
yes you do. if you make a statement, you need to back it up.
you seem to be new here.
these are the positions we're talking about.
@theorytoe
"containers provide no security"
https://ak.kyaruc.moe/objects/54f43667-3aee-4554-b660-bf52244282cf
---
@bonifartius
"containers provide absolutely no additional security."
https://qoto.org/@bonifartius/111844030509857526
i'm still waiting for the defenders to provide evidence for their claims.
i asked for real-life examples of hacked-processes breaking out of isolation.
@theorytoe@ak.kyaruc.moe @bonifartius@qoto.org @dcc@annihilation.social @mk@mastodon.satoshishop.de yep, been running some stuff via lxc on my proxmox server, works great, the only reason I'm not ditching VMs and using it for everything is related to backup speed.
Meanwhile using docker has always been an incredibly frustrating effort for everything beyond the basics.
@theorytoe @dcc @dotnet @bonifartius
please don't use docker without docker-compose !
@dotnet @theorytoe @dcc @bonifartius
"I'm not here to debate with you"
if you're not here to debate, why are you making arguments then?
what's your position? you need to be a software developer to use software?
do i airplane pilots need to know how to build jet-engines?
you're argument is retarded.
you can fuck off now.
@mk@mastodon.satoshishop.de @dcc@annihilation.social @theorytoe@ak.kyaruc.moe @bonifartius@qoto.org I'm not here to debate with you, I'm just responding to the original post about docker being terrible. It's like this, but backwards in that it's less frustrating to spin up two separate VMs than to deal with docker.
@lamp @theorytoe @dcc @bonifartius
"docker is not intended for security, it's not really any more secure than well configured services on systemd."
this is the position regarding docker/container-security:
"containers provide absolutely no additional security."
https://mastodon.satoshishop.de/@mk/111848424350713865
---
i don't speculate with you on what retarded extra shit is more or less secure.
"containers provide absolutely no additional security."
https://mastodon.satoshishop.de/@mk/111848424350713865
do you agree or disagree with this statement?
@lamp @theorytoe @dcc @bonifartius
yes i use mean word, but i'm still the most reasonable person here.
@lamp @theorytoe @dcc @bonifartius
"no, containers add some security"
thank you very much. you are correct.
you are the FIRST person to acknowledge that in this whole shitshow of a thread.
the levels of retardation in all of these people is absolutely astonishing.
@lamp @theorytoe @dcc @bonifartius
"docker is focused on functionality so it sacrifies some security for privileged features like host networking."
i agree with that.
@dcc love the memery! :ultra_fast_parrot: @theorytoe @mk
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.