Let’s be honest, if you’re a software engineer, you know where all this compute and power consumption is going. While it’s popular to blame #LLMs, y’all know how much is wasted on #docker, microservices, overscaled #kubernetes, spark/databricks and other unnecessary big data tech. It’s long past time we’re honest with the public about how much our practices are hurting the climate, and stop looking for scapegoats https://thereader.mitpress.mit.edu/the-staggering-ecological-impacts-of-computation-and-the-cloud/
This version introduces two major new features: new #Diagram application & 2 factor authentication using time-based one-time passwords (#TOTP). 🔐 We are now also supporting officially #Docker deployments. 🐳
We added a feature to easily destroy documents, fixed issues with #Forms & OnlyOffice documents. Under the hood we updated dependencies (#CKEditor, #Mermaid) & finally got rid of Bower. 👋🏻
First of all, let me assure you that I truly appreciate your work. Releasing software under a free license is a gift to us all. It shows that you care about the widespread adoption of your project, and that's quite commendable. However, I have a humble request – please, pretty please, don't release it with the statement, "compiling it is so complex and full of dependencies that the way to use my program is 'docker compose up'."
By doing this, you're limiting access to your software for those who can't use Docker or those who can't/won't use Linux. It's almost like telling someone to click on 'Install.exe.' Surely, you can do better than that.
I trust you'll consider my request. Thanks again for your hard work!
Hi all, I've just migrated from @irfan to this account on sakurajima.social. I'll also be attempting to migrate my main account @irfan to this one in the coming days, but I'm expecting nothing on that front since it's failed so far.
I've moved to multiple servers throughout my time on the #Fediverse in pursuit for a "permanent" instance to be on, and I've never had the chance to write an #intro post lol so this will be my first.
I'm a 26 year old (in Nov 2024) (gfdi) programmer obsessed with languages such as #Python and #Shell, frameworks like #Django, and #CloudNative shenanigans like #Docker, #Kubernetes, and #Helm. I'm also obsessed with #FOSS and #Linux, and promoting them to be more viable each day for the masses so everyone could have not just free but secure access to daily computing.
I'll be using this account to mostly document my passions through mini reviews or rants. I have another picture-based account over on #Pixelfed, @irfan. All images I have posted and will be posting will include descriptive/alt text, including my pfp and banner. I also have some bots for posting local (to me, #Malaysia) #news and other relevant data cos the #Mastodon API is just so fun to play with.
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!
in #flohmarkt haben wir jetzt dank @waaaaargh eine funktionierende docker-compose.yaml. In der README.md unter Installation→Docker ist beschrieben, wie man sich lokal einen flohmarkt zum entwickeln damit startet :) das #docker setup deckt datenbank und webserver ab und startet einen #mailhog, der die gesandten mails für euch entgegennimmt und im webbrowser verfuegbar macht. Damit sollte es für viele von Euch möglich werden, mit #flohmarkt herumzuspielen. codebase hier https://codeberg.org/grindhold/flohmarkt
First, #Docker transformed containers into a universally useful technology. Today, its development tools make it easy to create, package, and ship programs across all platforms. opensourcewatch.beehiiv.com/p/docker-sof... by @sjvn
I found finally a better way to build #php Docker images, no compiling required, smaller image than alpine, but still glibc so no incompatibilities or performance problems with PHP. How? It's possible with Wolfi-OS by @chainguard_dev
One of the interesting properties of #container registries is that they're essentially just big file stores.
This means you can use them to store and retrieve pretty much anything.
One idea is, if for example you need a specific binary on a host, you can just pull it from any container image, as long as you know the file location.
Are you using #Docker / #containerd / #runc? Congratulations, you won a full container breakout vulnerability via leaked file descriptors that can "lead to full control of the host system".
Allez, après des heures sur moteurs de recherche, forums, StackOverflow &co je demande ici, Masto, fait ta magie !
J'ai plusieurs machines qui me servent à build/lancer des containers avec #Docker. Sur toutes, le repertoire /var/lib/docker/overlays2 ne cesse de grandir.
J'ai testé toutes les méthodes de prune ($ docker system prune) avec les variantes (force, volume, images, builder, container, etc). Au final j'ai plus rien sur une machine là: 0 containers, 0 images, 0 volumes, 0 build cache et... le dossier overlays fait plus de 100Go.
Je sais que je pourrais arrêter le service, faire carrément un rm de /var/lib/docker/* et ça le ferait, mais y a aucun moyen moins crado de dire à Docker de nettoyer ses layers à la fin ?
🧨 We’ve partnered with the DDEV Foundation to support Lagoon workflows in #DDEV local development environments! 🧨
The result - a webinar packed with information, insights, and learnings so you can find out how to combine the best application hosting with a great local development environment to accelerate your workflow.
DDEV is an open source, #Docker-based development stack, perfect for #Drupal, #Laravel, and more!
Today's post is a #QGISServer update. It's been a while (12 years 😵) since I last posted about QGIS Server. It would be an understatement to say that things have evolved since then, not least due to the development of Docker which, Wikipedia tells me, was released 11 years ago. There have been multiple Docker images for QGIS Server provided by QGIS Community members over the years.
Installing kbin.social locally, anyone know what this issue might be?
Hey guys. I've been trying to get kbin.social running on my local machine outlined here but I'm running into issues...
Interact with Docker containers without leaving PhpStorm (dev.to)
In the previous article, I wrote about a particular setup you can use to configure Docker on WSL...