The Double-Edged Sword of Docker: Balancing Benefits and Risks
https://it-notes.dragas.net/2024/04/22/the-doubled-edge-sword-of-docker/
@alpalombo #docker ajuda muito muito mesmo :) usava #vagrant mas depois que conheci docker subir e testar as coisas local ficou muito mais simples.
In case anyone else ever has some fun with #docker and #libvirt / #kvm on #Linux 
By default the FORWARD table drops all packages...
To get vm's back on the net simply leverage #iptables to make the packets flow again:
$ sudo iptables -A FORWARD -i br0 -o br0 -j ACCEPT
You can install iptables-persistent to save the current ruleset so it is applied every time you restart the system. 😉
Did that on my #Debian workstation... I always fall for it. 😂
Yesterday's Jail/Zones call recording is up!
We discussed upcoming events, anti-FreeBSD FUD, @dch's OCI container progress and container registries, IPv6 networking and more!
Tonight Docker saved me a lot of time. I needed to recover a database from a backup. Instead of having a dump, I had the MySQL files directly. However, since they were from MySQL 5.5, they couldn't work with MySQL 8. Luckily, I found an old Docker container on Docker Hub with MySQL 5.5, and I was able to perform a dump in just a few minutes.
With so many #OpenSource projects offering #Docker as their primary way to use the app/service, it seems that the time will soon be upon me that I actually start to learn it. 🤔
Interesting reading: Kubernetes and back - Why I don't run distributed systems
https://www.davd.io/posts/2024-03-20-kubernetes-and-back-why-i-dont-run-distributed-systems/
@stefano @josephholsten And now.you know why my hate for #Docker and #Memenetes aka. #Kubernetes is growing and I just want a smol and stupid #Linux distro like OS/1337...
Typical modern software stack:
- They only provide a Dockerfile because it's so convoluted and patched together that it would be impossible to create a decent guide on how to make this stuff work without revealing just how much it's all held together by duct tape. Still, taking a peek at the Dockerfile will clearly reveal the chaos at play.
- Everything runs in separate containers, as it should, and they have automatic restarts, as they should. But then they're so tightly bound together with, you guessed it, duct tape, that when one of them fails, the container just restarts automatically, leaving the user wondering why everything failed, with only a cryptic error message.
- The main container is controlled by Supervisor - which is necessary because everything crashes very often, but the end user doesn't notice because Supervisor restarts the services. To outsiders, everything works fine (but occasionally throws some errors).
In short, the current trend is to sweep the dirt under the rug. A trendy rug, though!
#ModernSoftware #TechTrends #SoftwareStacks #Docker #Kubernetes #IT
The #FreeBSD developers need to look into the reasons why a vendor like iXsystems drops its support and usage for FreeBSD as one of its bases for their product. Don’t be mad about it. Analyse what Linux delivers better than FreeBSD and fix it. Is it #Docker, better hardware support or other things that are needed to be the choice today. Keep changing, adapting or you will be obsolete one day. In my opinion it still has the power to serve.
Ah, obviously. #docker only gets along with #firewalld if the latter is using the iptables backend (not the higher performing nftables default).
The #iptables backend is depreciated and slated for removal.
And of course there's no error message if configured "incorrectly", just random breakage that one then gets to debug!
I hate computers. I wish I was good enough at something else.
I'm only dealing with #docker because #nextcloud 's all-in-one container deployment requires it (it can't natively talk to #podman).
And yes, most of this (not docker) is true open source and I could fix it myself ...
But I wish there was a good collective bug/feature bounty program so we could all pool resources, you know?
Sometimes, I don't want to get dragged down yet another rabbit hole.
Any software developers who can maybe help me with the #WSL issue I posted here?
https://github.com/microsoft/WSL/issues/11273?utm_source=Mastodon
Software installation is to complicated. Lets use #docker.
Managing docker is to complicated. Lets use #kubernetes.
Managing kubernetes is to complicated. Lets use #portainer.
to be continued … 🖕
@lproven @theregister Plan9 is an #opensource OS with 38 system calls & few #linesofcode . Is not #UNIX . Need #Linux for VM only, to allow plan9 to run existing programs #mx #cluster #systemcalls #plan9 #filesystem #containers #docker #9front #kubernetes #snap #flatpak #git #unix #inferno #leansoftware #Oberon #a2 #multithreading #debian12 #Chrome #linesofcode #moreslaw #andalslaw #parallel_programming #softwaredevelopment #macOS #hypervisor #MicroVM #cubesos #linuxvm #pixie #zen #VMWare
slirp4netns is this weird thing for unprivileged network namespaces:
https://github.com/rootless-containers/slirp4netns
It's required by #podman because it runs without root privs.
The #RISCV in #QEMU thing also works with classic #docker, but I'd rather use Podman for improved isolation.
Uuuund ins Image eingebaut!
Uuuund weg mit der Entwicklungsumgebung!
Also hier: hcloud server delete <server>
#Docker #HetznerCloud
#SchenklRadioLeaks
![#23 [19/20] RUN mkdir -p /etc/firefox/policies
#23 DONE 0.3s
#24 [20/20] ADD conf/firefox/policies.json /etc/firefox/policies/policies.json
#24 DONE 0.0s
#25 exporting to image
#25 exporting layers 0.0s done
#25 writing image sha256:f9fc849c721b97ca7329e8c8e2cd932ff1db27df2f9d279](https://assets.chaos.social/media_attachments/files/111/823/285/924/525/236/original/ee0a546708913b43.png "#23 [19/20] RUN mkdir -p /etc/firefox/policies
#23 DONE 0.3s
#24 [20/20] ADD conf/firefox/policies.json /etc/firefox/policies/policies.json
#24 DONE 0.0s
#25 exporting to image
#25 exporting layers 0.0s done
#25 writing image sha256:f9fc849c721b97ca7329e8c8e2cd932ff1db27df2f9d279")
In this article, I described and updated how important directories are placed externally in #TrueNAS or #FreeBSD in order to store data independently of the jail. So I can refer to it again and again in other articles.
Similar to #Docker, the aim is to be as little dependent on the jail itself as possible.
Wie in #TrueNAS oder #FreeBSD wichtige Verzeichnisse nach außen gelegt werden, um Daten unabhängig von der Jail zu speichern, hatte ich in diesem Artikel beschrieben und nochmals aktualisiert. So kann ich auch in anderen Artikeln immer wieder darauf verweisen.
Ziel ist es, ähnlich wie bei #Docker, so wenig wie möglich vom Jail selbst abhängig zu sein.
https://bsdbox.de/artikel/tipps/freebsd-nullfs
@alelab @vermaden @0x1eef
Ran it via #Docker
Works quite well if selfhosted is a possibility 😎
Btw: https://searx.space/
@housepanther whats the differences to #docker?