Do I need a computer science degree to understand this?
 CRIME Shirt $21.68 |
 DMT Has Friends For Me Shirt $21.68 |
CRIME Shirt $21.68 |
Do I need a computer science degree to understand this?
Do I need a computer science degree to understand this?
CRIME Shirt $21.68 |
DMT Has Friends For Me Shirt $21.68 |
CRIME Shirt $21.68 |
The logo tells you everything you need to know about it.
WOW! HOT a What Baabhabhiat! Holy cow! Sukdeep is so mad he made a whole new thread about his overflowing seethe.
I am a brahmin. Shut the frick up before I poop on your desk.
What does that mean? I don't know the Jeets ranks
>To use
No
>To understand
Depends on the level of understanding. A rudimentary understanding, no. If you want to fully understand all of its intricacies, yes. That or just a generally high IQ in lew of a degree.
>If you want to fully understand all of its intricacies, yes.
LOL no you're a moron. docker is so simple it's ridiculous. you don't need a cs for anything tech related, are you a little kid?
>black and white splitting goy Black person npc golem
Holy frick knowing that 99% of humanity is human trash like you makes me feel better about myself.
Your reading comprehension is horrible. Maybe if you had a degree it would improve.
docker doesn't require a degree you moron. tell me specifically which intricacies require a degree. tell me, you won't. you're a moron
Explain to me how kernel emulation works
>i need to understand kernel emulation to understand how to use docker
get a load of this idiot
Explain very carefully in your own words what you don't understand in
>To use
>No
>To understand
>Depends on the level of understanding.
Write a quick start guide for Windows. Not authoring a container, just something simple like ooba or SD.
The irony is that you sound like a midwit teenager
>doesn't understand docker at all
I NEED TO REINVENT THE WHEEL MYSELF TO UNDERSTAND THE WHEEL
>good morning dear compootar and holy cow dung is magick gift krisha give to us praise krishna no need for understand
>in lew
holy shit you're a fricking moron
No, you need a computer science degree and 5+ (10 preferred) years experience working in DevOps/Cloud Engineer/Azure/SASS/ERP/AWS/Google Cloud PlatformReact/Vue/MySQL/Tomcat 7 and Microsoft Office
I fell asleep reading that. You were saying?
Is that chicken going to be okay?
>man docker
>arch wiki
>ChatGPT: <insert question>
It's never been easier to learn anything
This
Also use podman over docker
no one uses podman, sorry
I use podman so you must be wrong.
Yeah but you're a nobody
Idk, if something is so complicated that I'm told to run it in docker, that's a pretty good sign for me to not use whatever it is.
this makes no sense, and only proves you're a moron who thinks he's smarter than he is
if you need docker to run your application then it's shit
oh? explain why
Imagine writing an application which requires an environment to run that can't be replicated on a regular server.
How bad do you have to be at writing software to see docker as the solution to this problem?
What if you need two applications which need two conflicting environments?
Rent another server?
>conflicting environments
I never had this problem and what exactly would be the conflict? Python, Java or some shitty library?
>I never had this problem
you don't understand what docker is for lol
yeah it's for shitty applications that were made by shitty developers for shitty admins
why was docker made for shitty applications? can you even explain why?
>Imagine writing an application which requires an environment to run that can't be replicated on a regular server.
suppose i want to run your app and don't give a single shit how it's constructed nor do i want to. docker. now let's suppose i have an entire stack i want to run that has 7 or 8 apps that all work together. docker. are you really so stupid that you can't figure this out? get a job you fricking pathetic unemployed homosexual. DUHHHH JUST BECAUSE I DONT GET IT MEANS NO ONE SHOULD USE IT DUHHHH you fricking absolute nitwit moron
Imagine all the application you write are such basic b***h shit that never ran into those issues, lmao.
Have you even touched a GPU once in your life?
skill issue
I don't control the shit code other people write. I need an container environment to encapsulate other people's shit.
Does any CS degree even specifically teach containerization? Closest thing I got was virtual machines
you copy and paste a docker run command and it just werks, you don't need to know more
What's the right way to learn docker? From the ground up, assuming no prior knowledge, to being able to use and understand it at a practical level and beyond.
I've never used docker before, and I am not worried about using docker. This isn't just hubris either. The real hubris comes from thinking I will just learn Rust and be good at it.
It's just a bunch of config files, right? How hard could it possibly be.
to learn rust you must first take HRT and cut your diick off.
I just had surgery and both of my balls and penis are still intact. I still have my natural manboobs too.
Docker has an official tutorial on their website that is easy to follow.
Just take whatever backend project you have lying around and set it up to run with Docker.
>buy a shitty $60 refurbished TMM box or thin client
>install something basic on it, like debian or rocky (make sure you research docker vs podman and pick a distro with good OOTB support for it, I'd personally recommend podman since there's a general move in that direction)
>go to /hsg/
>find some shit you think could be nice to have on your network (like jellyfin or vaultwarden or whatever)
>find a prebuilt container
>using docs, figure out how to write a docker command that runs it, then turn it into a compose.yml, then turn that into a systemd service
>once you're comfortable with that, take something else and write your own dockerfile for it
there's your beginner guide, should teach you enough to figure out where to go next
I have a CS degree and I have no idea how it works or why you would need to use it.
With docker you write dependencies directly into the docker image container and it requires no setup for anyone who will develop as the image container will be 1:1 representation of whatever you are building no matter where it is deployed.
You can't do the same with just providing the source files, which has many assumptions about the environment it will run in, typically resulting in the need for explanation on how to setup up proper installation.
For smaller setups it isn't that relevant, but if you are dealing with a big project that interfaces with a lot of different spaces you should always use Docker so you don't run into this issue. Of course, with this in mind you should be able to understand why even for personal local development it is a big advantage for development to be image based.
if you can't manage fricking dependencies for your fricking application to the point that you need docker you should just have a nice day
snap replaces docker entirely
die
now that's just moronic
Who is publishing their website on the Canonical controlled Snap store?
To understand the usecase you simply need install a server software and it's dependencies a few times. Now you realize how much pain in the ass it is to do this by hand, and containers standardize the act into it just werks.
your distro is just shit and the software you run is just as shit as the distro
it's a glorified chroot. I fricking hate it. the only thing I hate even more is k8s. docker/k8s in job description means absolute hell, especially for developers.
Do you like a spaghetti in code? And deploy via FTP or something worse? Many servers which must be the same? If no for anything, then you know the reason for Docker.
tfw: working with it now.
Yeah, I know the reason for docker/k8s, but still hate it. These usually imply micro-service architecture, and it's a b***h to develop for. I spend more time diagnosing problems in fricked up deployment environments that actually coding. It's a necessary evil, I guess.
>I spend more time diagnosing problems in fricked up deployment environments that actually coding
Welcome to REAL coding for REAL job-having adults, sweetie
I've been doing this for 18 years. Things weren't this bad when I was starting, or even 10 years ago. I definitely wouldn't choose this career again, in today's tech landscape.
>I've been doing this for 18 years.
you seem pretty bad at it. the mount of years you've been doing something has nothing to do with how good you are at it. and i can see from your shitty attitude and moronic takes that you're really bad at what you do. if you don't understand docker, and don't use it, it's just more evidence to the fact that you suck and aren't good at what you do and don't understand simple concepts. you are stuck in the old world, i bet you make shit apps, or no apps. are you an old style sysadmin? nah, i bet you're unemployed
>you seem pretty bad at it
possibly
>you don't understand docker, and don't use it
I have to understand it, because I use it every day
>you are stuck in the old world
yep
>i bet you make shit apps
it's pretty likely some of code I wrote was involved in delivering your shitty comment to this board
>are you an old style sysadmin?
nope, system programmer
>nah, i bet you're unemployed
huh, I wish
>shitty attitude
Go back to
kiddie
>Do I need a computer science degree to understand this
Docker is a comp sci pathology similar to java. A desire to have a certain way of doing things taken to absurdity - in the case of java that's unnecessary verbosity of language. In the case of docker, unnecessary abstraction. When you big boy deploy a python environment in a docker on AWS, you're running a python environment in a python environment on a VM on a VM on a VM, so you can virtualize while you virtualize while you virtualize in virtualizing. Ultimately, clean well-maintained libraries on bare metal.. worked for decades, no reason it shouldn't work fine now.
nothing to learn or care about there.
ITT: DUHHHHHHH I DONT UNDERSTAND HOW TO USE DOCKER DUHHHHHHHHHHHHH IT'S SO HARD DUHHHHHHHHHHHHHH IM A DUMBBELL DUHHHHHHHHHHHH
It's like driving stick. You don't need to know how how the gear box works or how the clutch syncs the gears, all you need to know to drive it is how to put it in gear and how to time the gas and clutch correctly.
you're in luck OP. this just landed.
>use snap
>use appimage
same program as is in docker but it just works
no dealing with badly configured docker packages
I uninstall docker on every server I work on
docker and snap/appimage are not even the same thing or the same purpose. are you really this fricking stupid LOL
>he hasn't yet simulated his own containerization with Linux namespaces, overlay file systems and virtual network interfaces
Ngmi
It's actually a prime example of incredibly easy to understand and use software that's completely ruined by dog shit manuals, cli and people's attitude towards it
If you have to ask IQfy about having a degree in CS for something clearly not related to CS you have bigger things to worry about
It's just a fancy chroot.
crazy seeing how moronic devs are
I have never used docker before and want to use it since a lot of people keep saying it is important. Can anyone explain it to me how it works and do I really need it? I only want to make a simple crud backend.
the concept of docker is quite simple. The execution is quite poor & confusing.
its a glorified .rar ("docker image")
the glory is, that it is a self contained run environment, having backed in all the requirements, including the OS, which can be altogether different from the host os.
docker compose orchestrates multiple docker images, you can configure networking, restart policies, mounting in directories/files, declare the order of starting (depends_on relations), health checks for automatic restarts, etc.
alternatively, you can use gayass kubernetes, which comes with its own lingo (services, deployments, config maps, etc. all yaml config files)
you are welcome! no go to the cloud and become a god. enjoy milking all the shekels off of the goy cattle.
Its just a headless linux vm. whys is it so hard to understand, boomer?