you're bloat is ready, sir
dont talk shit about docker
>>86930429>bloatif you use go, it's a scratch imageFROM scratchCOPY /app /appENTRYPOINT ["/app"]
FROM scratchCOPY /app /appENTRYPOINT ["/app"]
>>86930429>You're bloatI am not bloat, in fact, I'm quite skinny.
daemonless?rootless?but of course!
>>86930525>but most importantly>useless!
>>86930525You vill live in ze pod
>>86930525>pull a docker image>can't spin up a container because it uses root to do everything
>>86930573that's not what rootless means, but ok
uuuurggh too many container
>>86930458>no TLS certificates cool fizzbuzz, brotato
>>86930604sir you don't have the permission to shill podman on /g/, you need to be contained
>>86931138>setting tls in container levelngmi
Remove the whale, that's all you need.
>uses spoon for everything>THESE FORKS ARE JUST BLOATjust because you don't use all the features doesn't mean it's bloat, it just means your retarded
>>86931138>Dealing with tls at the containerEven if its a monolith its still retarded
wtf is docker?
>>86931457When 2 homosexual males touch wieners
>>86931457- containers- containers- containers
>>86931457Something that attempted to solve a long standing problem in the software industry that just ended up making new problems
>>86930517Context: ..in this case: ....bloat means untidy;
>>86932589you just described linux
>>86932589People were using containers long before Docker.
>>86932654>>86932654it doesnt stop at linux.its really the entire history of software.
>>86930429your bottleneck I/O throughput than just running it on bare metal is ready sir.
>>86931457a plan 9 feature finally brought to consumer computers 25 fucking years later, and not even close to being as good
>>86930429Nix doesn't have this problem
>>86933004it's far worse actually
>>86933343>lying on the internet
>>86933433>>86933491Enjoy your wasted storage
>>86933493>Nix>every library is shared as much as possible, resulting in minimal disk usage>Container trash>everyone uses their own bloated base image, resulting in tenfold duplication of libraries
>>86933529>/nix is still 80GB even with garbage cleaning>builds need 15-20GBI don't know how they do it but it takes a shitton of storage
>>86933555If you're doing heavy builds and leaving gcroots everywhere you're going to use a lot of storage, that holds true even without Nix.
>>86931138lol this cant be real
>find neat new software>only method of installation is a Docker container
>>86930429based docker making library trannys seethe
>>86930429Works on my machine
>>86933737Trannies love docker, properly installing software is for straight men
>>86933883docker is loved by every linux server system administrator
ITT: unemployed retards
>>86933893Because they're all lazy trannies
>>86933915Sure m8. Are those lazy trannies in the room with us right now?
this shit saved me literally days of work hours and Im not even the one who has to build and mantain itdocker that is, jenkins is garbage>>86930458holy based
Docker is good to be honest.just sudo docker-compse up this bitch and your done.
>>86933004redpill me on nix, been thinking to switch to it for daily driver as well
>>86930429virtualization is for pussiesrun everything on bare metalcrashes are part of the sysadmin experience
>>86933940>builds take gigabytes of memory, crash on systems with less RAM (https://github.com/NixOS/nixpkgs/issues/38635)>takes 20-30GB extra storage compared to regular distros>the Nix language is dogshit, even it's creator acknowledges it was a mistake (https://discourse.nixos.org/t/alternative-language/5218/11)>shit tooling>shit docs>needs ELF binary patching for a lot of software>appimages need appimage-run, a special wrapper to run>some packages need hacky workarounds (like steam-run) just to work at all on the non-FHS compliant filesystem hierarchyit's pretty shit, Guix is better in some aspects but I wouldn't recommend eithert. ex Guix user
>>86934013>some packages need hacky workarounds
>>86933966Docker is not virtualization, stupid.
>>86934031mfw didn't proofread 4chin replymeant containerization, still applies
Jenkins is the ultimate bloat.a bash script is better than Jenkins for deploymenrt
>>86934491you can't disprove a single one of those points, cope
>>86934543>builds take gigabytes of memory, crash on systems with less RAM (https://github.com/NixOS/nixpkgs/issues/38635)That has nothing to do with building, it's simply misusing Nix. Do dumb shit, get dumb results. Use nix search.>takes 20-30GB extra storage compared to regular distrosYou have no proof for this.>the Nix language is dogshit, even it's creator acknowledges it was a mistake (https://discourse.nixos.org/t/alternative-language/5218/11)"Not that great" is a far stretch from "dogshit". If anything, it is commendable that the author criticizes his own work.>shit toolingBaseless claim.>shit docsBaseless claim.>needs ELF binary patching for a lot of softwareOnly shitty proprietary software.>appimages need appimage-run, a special wrapper to runSame problem as proprietary software because AppImages are dynamically linked binary deployments. The same breakage will happen on FHS distros sooner or later. Nix reveals this flaw instead of shoving it under the carpet.>some packages need hacky workarounds (like steam-run) just to work at all on the non-FHS compliant filesystem hierarchyAgain, only software distributed exclusively as binary has this problem. FHS is the cause of many issues that exist in software deployment that Nix has fixed. FHS binaries breaking under different circumstances is yet more proof of how shitty FHS-style deployments are.
>>86930429Explain precisely what's bloated about it?
>>86932850Doesn't happen on Linux.
why should I care about docker as a non-programmer, again?
>>86934607hypermegacope, typical of nixxers
>>86934607>Same problem as proprietary software because AppImages are dynamically linked binary deploymentsThe problem with emulating .app and .exe is ignorance to the fact that these binaries link to their respective operating systems, dozens of gigabytes in size, and use their apis explicitly. There can be no appimages unless (1) the kernel magically gains huge bloated userspace utilities essential to every baseline linux machine and can't be disabled by a compile flag, (2) appimages bloat up to gigabytes, or (3) require the installation of a base runtime appimages then link to.Electron for example went with (2), but (3) in my opinion is what both electron and appimages should have done.>>86935163Seethe harder brainlet
>>86930456I do like muh bloat. Thankyou :)
>>86931446>>86931425>>86931138have you tried to run cosmosdb from docker container and you were able to solve cert problem? Its a nightmare. Tons of people have problem with it, and those idiots cant answer why cosmosdb HAS to run locally with httpshttps://github.com/Azure/azure-cosmos-dotnet-v3/issues/1232
>>86934607"bloat"It's 2022This is hardly a lot of space>>86935124It makes piracy easy, and comfy
>>86934527can you integrate bash with your git repository, so it runs tests on every push, and sends you mail with results?
>>86930429docker is based tho
>>86935252>It makes piracy easy, and comfyplease do elaboratei'm intrigued
>>86930429Bloat is running separate VMs bro. Docker is a way for a system which you plan to keep running for years.
>>86935266Not that anon, but you probably could with git-hooks + the mail cli.https://git-scm.com/docs/githooks#post-receiveYou can do all sorts of things with git-hooks, no one ever reads the docs tho.
>>86934527Oh really? Show me one, a real one that deploys something that makes money.
>>86935211kek what a clusterfuck. seems like the maintainers felt kinda apprehensive to let people test it at their own pc and rather have them use the one hosted by azure. but that's bad advertising. wonder why people are still cucked to use ms azure services.
>>86935266Yes, look into git-hooks newgen
>>86931138this is your average /g/ poster
>>86935313Browse movies. tv via overseer to add to Sonarr, Radarr to trigger search withnzbhydra/jackett to manage and do searchs with indexers connected to Glutton to handle VPN to bypass ISP blocks of torrent sites. Jackett returns searches to sonarr/radarr who select the torrent based on my preference and send it do be downloaded.Everything in separate containers. Each container is updated independently no miss matched requirements, just works.It's just a nice way of managing stuff IMO. You can run all that on bare metal but I just find it easier to do with docker. it's all clickily boxy or one like docker commands
>>86935442>ISP blocks of torrent sitesbig uffdunno, everything you said looks a bit like overdoing it... just for some contentmaybe i'm missing the pointi just... know of something i wanna get, download from my private tracker of choice, seed and enjoy...
If i want to watch the lost city I just click request, and I'll get an email when it's done. I don't really download movies though, that's just an example. it's more useful for TV shows sonarr will download new episodes at the quality I want, when they appear.
>>86935442im always so jelly of elaborate home media server setupts like this. i wish i actually enjoyed watching movies just so i could justify working on something like this.
>>86935593to the tune of>why spend 5 min solving an issue when you cand spend a week automating a fixbut jokes aside, yeah... cool setup you got therei imagine it being a nightmare maintaining in working order, but i guess that's what docker is solving for you
>>86935442interesting, do you use docker-compose?Those services support streaming?If you know kubernetes i guess it would be pretty straightforward to create cluster with all those services, and made a portal with pirated movies as ghetto alternative to netflix and even earn some money. Or do fetish porn site out of it, if you are into that sort of thing
>>86930429docker is literally like hiring another hooker just so she can watch the clock and remind you how long you've been with the one you're fucking.
>>86935669Have you ever used docker?
>>86935608You can do it with a pi and a hard drive, or an optiplex or something. >>86935642>a week There's little setup involved when you use docker and yacht/portainer to manage containers.Here's an example, of how little work it is to actually "deploy" a container.All the setup for the major things like sonarr, radarr is done through an easy to use webui, it takes minutes.
>>86935690There's plenty of guides to doing this type of thing. I recon someone who isn't even comfortable with linux and CLI could buy a pi and a big hard drive and be setup in under an hour if they just follow a guidehttps://www.youtube.com/watch?v=5rtGBwBuzQE
>>86935690thanks for taking the time to record and show this to us, anonthe subject in general is pretty foreign to me (hence my presence ITT)i guess looking into this might be a vector of approaching it
>>86935685I've used your mom
>>86935608Why would you be jealous of someone wasting time in order to waste more time?
>>86935929because i like fiddling with computers...
>>86935929how is learning and tinkering and making stuff happen a waste of time?what else would life be about?
>>86935211>using vendor specific servicesyou tards are the same type of tards who married microsoft in the early 90s
>>86931432they pretty much did. the new logo is so abstract, the whale is barely recognizable.
>>86933729that software probably meant to be ran 24/7 anyway and you were probably trying to run a server from your desktop like a retard or your personal server setup is so boomer you're managing it's shit with apt
>>86934013hmm, i have 8gb of ram so it would be ok ig>extra storageshouldn't be a problem>shit tooling and docsi read some parts of docs, seemed neat, idk about tooling>elf binary patchingwtf is that>appimagesi don't use those so>hacky workaroundswill look into this, thx>>86934607hmm thanks my suspects are clear, guess i am gonna give nix a try, i am tired of rolling-release...
>>86935991Life is about finding your calling to improve the world, you could be working on fixing the 50+ things wrong with tech you cope and seethe about on /g/ every day but instead you're wasting all your time making a consoomer station and the rest of your time consooming
>>86931457>"works on my machine">ok then ship your entre machine
>>86930429LITERALLY me at my job lol. "It's just werks" is my tech lead's motto.
>>86931425>>86931446>>86933683>>86935416Okay then faggots, how should I be doing. I know that none of you will reply to this post because it's clear none of you understand what you're talking about.
>>86937198They will say you should terminate TLS at the gateway and use insecure HTTP for in-cluster networking, because they’re amateurs
>>86937222There's no way anyone is that fucking retarded.
>>86935690why exactly do you need them as docker images? can't those daemons just run as any other program without containers?
>>86935252Prowlarr can replace NZBHydra2 and Jackett.
>>86935535>dunno, everything you said looks a bit like overdoing it... just for some content>maybe i'm missing the pointNot that anon, but I run a similar setup. I share it with friends and family, they can go to a website (Overseerr) and request a new movie or show or something, and it shows up automatically within 20 minutes or so. It searches newsgroups and torrents and picks the best one, and handles all the searching, downloading, moving, renaming, and tells Plex to update itself. It emails the person that requested to tell them their download is ready, and it sends me a Telegram message so I can put the brakes on if someone requests every episode of General Hospital.>>86935643>interesting, do you use docker-compose?Anon has Portainer going, which is basically a web-based way to run docker-compose (with a lot more functionality). I keep my docker-compose files out in GitHub and have all my stacks linked there, so I can update the docker-compose if I want and Portainer will pull down the setup and update the stack. If I fuck it up, I can roll back the commit.>Those services support streaming?Plex and Jellyfin are for streaming. Most of the rest are for getting the content that Plex/Jellyfin streams to you.
Docker scares and confuses the tinker-tranny.
>>86935642>>why spend 5 min solving an issue when you cand spend a week automating a fixYou can spend 5 minutes downloading one movie you want to watch, but now I have a fully automated system that handles everything for me and has downloaded thousands of movies and TV shows for me. Plus I no longer get phone calls from people asking for this movie or that show, because they can do it themselves.
I do a nas with plex, radarr and slskd and it does piracy really easy amongst other things like game servers. That said i've probably spent more time fucking with it than I have saved.
>>86937894it just werks
>>86937589You don't NEED them as containers, but having them as containers separates the temporary/ephemeral data from the permanent data. You can move your Sonarr config directory to a new computer or new OS and just redownload the container and do your mappings and be back up in no time. The software install itself is throwaway.I run a cluster of servers all serving up the same stuff, and if one of the servers goes down or needs a reboot or something, one of the others recognizes the work isn't getting done and starts the container with the same data within a few seconds. It happens all the time in the middle of the night and I don't even notice.
>>86936435>that software probably meant to be ran 24/7Yes, that's what a daemon is for. I don't need a docker container for something to run constantly.>you were probably trying to run a server from your desktop like a retardOf course not, I have a proper home server.>your personal server setup is so boomer you're managing it's shit with aptOf course. Why would I use anything other than Debian stable for a server?
>>86937798NZBHydra2 and Jackett tends to work better for me. I tried Prowlarr and I don't even think I could get it to link to talk to flaresolver.
>>86930573t. Retard who never used podman
>>86938520>https://wiki.servarr.com/prowlarr/faq#can-i-use-flaresolverr-indexersSupposedly Flaresolverr/Prowlarr works, but none of my indexers require it so I don't run it myself. I had weird performance problems with Hydra, and also cert issues, both of which went away with Prowlarr.Don't know what was up with mine, but glad yours is working.
>>86939431Hydra does have some performance issues, if you have large logs it will star to use lots of memory (the dev couldn't figure it out the last time i read the github)But i dont keep the logs long so i didnt have that issue
>>86930525Not only will I live in the pod but I will apparently also run my code in it
>>86933729>Read the Dockerfile to see exactly what it is doing>Do the same shit by hand>I R 1337 H4K3R
>>86939959Is it just a script I can replicate without Docker? I'll have to look into that.
>>86932589What was the problem? People couldn't just whip up bash scripts to setup local test environments?
>>86936011>verbally assaultedKind of redundant. Plus, I don't think that is technically assault.
>>86940419Dockerfile has about 4 important directives : >FROM the base container>ADD copy files into the container>RUN a program or script that is to be run to setup the container>ENTRYPOINT the program that is run when the container is runEverything else is about what directories or sockets or IPs the container expects when it is run.If you can't figure out what a Dockerfile is doing based on the above you shouldn't be installing shit by hand.
>>86930429seriously, my boss wrapped nearly all of our processes in a container. I found docker using 15 gig of ram on my dev laptop. My dev laptop only has 16 gigs of ram. 5 fucking containers for a web app.
>>86930429>you're bloat is ready, siryou don't even understand what docker is, do you. docker is only as bloated as the shit you put in it. docker is just a process, literally exactly like the process you run without docker. so docker isn't bloated, YOU are bloated. fucking stupid techlet FAGGOT.
>>86931138DUHHHHHHH IM A TECHLET, I DON'T UNDERSTAND THAT CERTS DON'T LIVE AT THE SERVICE LEVEL DUHHHHHHHHHDUHHHHHHH IM JUST GANNA SAY SHIT ABOUT THINGS I DON"T UNDERSTAND DUHHHHHHHHHHHHDUHHHHHH IM UNEMPLOYED, THIS THING I DON'T UNDERSTAND IS STUPID BECAUSE I DON"T UNDERSTAND IT DUUHHHHHHHHHH
>>86941553kek you're so confident but so retarded at the same time, it's delicious. they clearly meant system CA certificatesnext time check yourself before you wreck yourself
>>86941638>DUHHHHH IM A TECHLETyou're a fucking stupid idiot MURDER YOURSELF
>>86941690seethe neet, read some books and you might understand what the adults are talking about
>>86941638he literally meant SSL, you stupid fucking piece of trash
>>86941774you're embarrassing yourself
>>86941854>retard image poster>got caught/g/ users are fucking stupid. post your salary and job title you stupid retard
>>86930429k8s is pretty based, senpai
>>86941908you expect retarded OP to understand k8s when he can't even understand docker? LOL. all anti docker retards are the most stupid tech idiots on the planet. they don't have jobs
>>86941774I sure wonder what CA certificates are used for. Couldn't be SSL.
>>86930429I can replace you with:-option #1: chroot-option #2: local grade VM ala virtualbox-option #3: dont be a pussy and do your job right deploying a fucking server. When trannies use free bloated IDEs ala netBeans or eclipse but can't waste 50 bucks and a couple of hours to do their fucking job right in the first place.inb4 You tards destroyed nebeans and eclipse in the first place.
i figured out how to run a jupyter notebook from inside the docker a few days ago, but the dependencies are fucked so it doesn't work and the guy who made it seems to have fucked off. i bet this could be really convenient, when it's actually packaged and documented properly.
docker-compose is great for media fag shit
>>86930429Ahoy mateys, we'll get to bloatmax in no time with me at the helm. ARRG.
docker puts techlet retards out of a job
neckbeards will never recover, servers are too easy now. nobody needs a neckbeard
>>86943092what is this dashboard?
>>86934527>>86935349At my work, all CI/Deployment is done via thousands of lines of bash, and I can assure you we make money, though we are a smaller company, <50 devs. It is somewhat manual, because there is a person who looks at all the MRs every day and decides which ones to put into the next production build which will be used the next day.I have been working on migrating the stuff the Jenkins. I have found it frustrating. I've never worked with Java/Groovy before. It took me a whole month to basically have the same stuff running as before but with a nice web UI. Also the servers we use for builds keep crashing because the OOM killer gets called -- memory spikes occasionally.
>>86943244this is completely pointless. kubernetes + flux or argo eliminates all of this nonsense.
>>86943349>kubernetesliterally meme tech
>>86936830This is the best answer.
>>86933927Yes I'm responding to one right now
>>86937222muh service mesh
>>86932951>a plan 9 feature finally brought to consumer computersI'm glad to not be the only who noticed that.Docker/Podman is the poor man version of a properly implemented namespace.
>>86932951>>86943579Research toy operating systems do be like that sometimes.
>>86943409explain how, i need a good laugh
>>86943409b-b-but it powers fighter jets!
>>86943928the f35 is a garbage fighter jet
>>86930525Based. I use it for tinkering with Proton builds without cluttering up my shit with all the bajillion different dependencies and versions of said dependencies. On a somewhat related note. Compile Proton GE custom with -O3 and -march=native. The performance in DirectX native games is actually unbelievable.
>>86943917doesn't run on windowsTXMAD
>>86935313Can you imagine being an inkwell
>>86942187Plenty of anti-docker retards have jobs, they are always asking me if I want fries with that.
>>86942741Is pyload the new meme downloader? I'm still on NZBGet and qBittorrent.
Using containers as an end user is a meme. The future is a mix between VMs and serverless.
>>86930573lmoa you don't understand anything about containers
>>86944078can you share what you're doing in more detail? this sounds pretty interesting and a good way to use containers
>>86932951>>86943579Every "modern solution" is an ass backwards take on something Plan 9 solved correctly 25 years ago.
>>86935763Did you dock her?
>>86936011I feel like wm4 was the one actually seething from the chat messages alone, if you ignored the funny drawings
>>86941534Docker is bloated because it takes more resources to do the same thing.
>>86941534Processes running inside docker are fundamentally bloated because they cannot reasonably reuse system libraries, meaning you will have a 2x duplication of libraries on disk and in memory in the best case.
>>86946959>OOOHHH NOOOOOOOOO IT'S A CONTAINER!!! WHAT AM I GOING TO DO??????run a vm? use flatpak? or a snap?docker just works on everything and has all the advantages
>>86946995Are you autistic? All the things you named have the same flaw as docker. None can share libraries between the OS and the application. This is massively bloated.
>>86946959>HURP DURP HOW DO LAYERS WORKstfu until you understand the tech you criticize
>>86947008I don't care for shared libraries that's why I said it's a container. Flatpak doesn't work on a server, snap is best used on ubuntu (and kinda sucks) and vms need resources permanently allocated which is a waste most of the time. Docker has non of those issues and all the advantages. It's a clean solution to the messy problem of dependencies and libraries on linux.
>>86947033Layers do not solve the 2x duplication issue. That's why I said in the best case. Even with layer sharing, there is at least a 2x duplication in libraries on disk and in memory, because layers cannot account for the libraries installed on the system. This also assumes that you're lucky enough to get perfect sharing with layers, which is a rare occurence because layers tend to be extremely coarse-grained. A DAG of dependencies or a per-file content-addressed storage system like the one Flatpak uses would be far more efficient.
>>86947073>Oh no muh wasted 5MB of Alpine imageHow will we ever recover from all this wastage
>>86947038Docker is not a clean solution by any means. It's a very crude and ad-hoc solution.
>>86947073DAG-based versioning systems are less universally adaptable. In particular they tend to fuck up and get extremely slow on NFS filesystems when they need to compute checksums.>>86947113Crude in this case meaning simple and universal.
>web dev general 2next please
>>86947113It's a clean solution to the problem it solves while being easy to mange and simple to use. The only reason why docker exists is because to many people got fed up with managing libraries.
>>86947121>DAG-based versioning systems are less universally adaptableHow?>In particular they tend to fuck up and get extremely slow on NFS filesystemsYou're not storing docker layers on fucking NFS.>when they need to compute checksums.Do you not know how docker layers work?
>>86930429If that type containerization is bloat what is the FOSS way secure applications listening on ports?>/You are running network services with security vulnerabilities in them./ Again, /you are running network services with security vulnerabilities in them/. If you're running a server, this is almost universally true.
>>86947328they don't have one/thread
>>86947136>containers for webshitfeel free to stop posting anytime