604
My lazy ass, nowadays.
(lemmy.ml)
Next evolution, just a one line bash script.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Feb 2024
604 points (95.6% liked)
linuxmemes
21031 readers
787 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Eh even as a Linux admin, I prefer hand installs I understand over mysterious docker black boxes that ship god knows what.
Sure, if I'm trialing something to see if it's worth my time, I'll spin up a container. But once it's time to actually deploy it, I do it by hand.
Same. Frustrating when you have to go digging for non-Docker instructions.
yes very much agreed on this. docker is awesome but imo the reliance on it will absolutely cause issues down the line
Sorry but IMO that’s FUD.
The reliance on it legitimately prevents the issues that it’s likely to cause. It’s made to be both idempotent and ephemeral.
Give an example of a Python project. You make a venv and do all your work in there. You then generate a requirements with all the versions pinned. You start build a container on a pinned version of alpine, or Ubuntu, or w/e. Wherever possible, you are pinning versions.
With best practices applied, result is that the image will be functionally the same regardless of what system builds it, though normally it gets built and stored on a registry like Docker Hub.
The only chance a user has to screw things up is in setting environment variables. That’s no different than ever before. At least now, they don’t have to worry about system or language-level dependencies introducing a breaking change.
If it’s an open-source project, usually the dockerfiles are available for reading.
Do you audit every line of code that you run in production? If you are trying some new python/django/sql app, are you reviewing all that?
I’d assume with a python based project, you’d be able to at least look at requirements and tell there’s something that sets off red flags. And you are either familiar/trust the maintainer, or you are reviewing the actual python itself?
Beyond that, the dockerfile is essentially just installation instructions for getting it running on a virgin system of X distribution. I wouldn’t call that a black box.
If the container isn’t part of an open source project, then this is a moot point then. The project itself is a black box.
You do you. Speaking for myself, I prefer to understand and be able to trivially inspect and modify the moving parts in the things I deploy so I have a snowball's chance in hell of debugging and fixing things when something inevitably goes wrong.
All I hear is FUD.
And all I see is someone taking this conversation way too personally.
You sound like someone who doesn’t want to save 10 minutes of work every day because it might cost you half an hour every month.