Maybe you mean it’s use where people use it specifically as a package manager

Precisely. Containerization is great and Docker does it well. Sending someone a reproducible script that can set up your software package for them is great. Marrying the two concepts unnecessarily and using one specific tool which is designed primarily to do the first, to instead do the second, is the only real issue I’m taking with it.

Yeah, I honestly just strongly dislike the whole Docker ethos. It was designed for one thing (deployment at scale), at which it excelled, and then everyone uses it for a different thing (reproducible one-off deployment), at which it is fine, basically, but just kind of the minimum set of capabilities to get the job done.

Nix can do what Docker does, in a much superior fashion (lower disk space, much better transparency, rollback ability, lack of towering chains of follow-on effects as you are talking about, and applications outside of mucking around with containerized images), but for some reason everyone uses Docker, and Nix is as far as I can tell unused outside of NixOS.

Whatever. When they make me king, it’ll be different, that’s all I can say.

I don’t think .ml should be ousted. I think they should stop being dickheads. It’s a little tangential to this particular post (mostly only relevant in that it makes people suspicious of their motives when otherwise they would not be.)

Yeah, it’s crazy how we all have more or less the exact same opinions, and the leader bans anyone who doesn’t have those opinions, and we’re all fine with it and in fact justify it and claim it’s right, whenever it comes up.

It’s totally insane. I have no idea how or why anyone would decide to make an account in our stuff. In fact, it makes other people suspicious of our designated good leader, even in scenarios where there isn’t otherwise a ton of reason to assume any malice.

Docker is a mediocre solution to a real problem. It doesn’t cost any money, it does the job, but also, it consumes lots more disk than it needs to and can’t do some things that a solution in this space really should be able to do.

If the world had decided that Nix was the way to containerize their web services and make them reproducible, the world would have been a better place, but that wasn’t what happened (yet at least).

• “This isn’t even malicious, just look at it, it’s perfectly innocent”
• “Besides, if they wanted to do something, they could disguise it way better than this”

Pick a lane, .ml.

I know, we don’t want our software sending our secrets to the trusted good leader, and we don’t feel like participating in places where only the leader’s viewpoint is acceptable. Unlike the non-sheep, who are fine with both those things apparently, because who wouldn’t trust the good leader.

They didn’t acknowledge it. They just silently fixed it (or, someone did, at least).

They’re not obligated to come in here and get yelled at, of course, and what would it accomplish. But, on the other hand, it is relevant that they can’t handle being in any environment where people can just speak freely to them, and respect is earned rather than demanded by force. There’s a certain type of mentality that just can’t cope with being in any role other than “the boss” and being able to talk down to or punish whoever they want, with no one allowed to express anything other than respect and obedience in the other direction. That is, in fact, the exact mentality that makes people suspicious of this otherwise maybe innocent issue with the software.

Edited.

Yeah 100%, it’s all Docker’s fault at the end of the day

One of the .ml users down below volunteered to put in the PR later tonight if no one else has, so it sounds like both bases are covered now.

Sounds great. Thank you, it sounds like a good idea.

Seems like a genuine miss, contrary to what the comments here would have one believe,

You might be right. I looked at the history and the way it came in, and it’s not as wildly anomalous to the rest of the file when looked at in context. Maybe it’s just a mistake.

Let’s not get carried away. Shared software systems are about more than the software. If you’re looking only at the software, and that was literally 100% of what is important here and nothing else, then yes, you’re right.

But you want it fixed less than you want it publicized

100%. Yes. Correct. I also want it fixed, but that’s completely trivial, with or without the pull request.

See the edit to the post.

Would have been nice with a link from the start.

Yeah, 100%. I edited the post to add more of the details.

I mean probably I should. There are a bunch of people accusing me of being dick headed and petty and they’re not completely wrong. Honestly, I just don’t feel like helping the Lemmy devs. Dessalines, at least, is totally unapologetic about being a dickhead to people he has power over. That puts me in a mindset where, mostly, I want to talk to other people about potential harm he’s in a position to do, and not really in a mindset where I want to do even a small amount of extra work on his behalf.

I’m going to tell other people that he’s in a position to take their passwords. If he wants to see that and put himself not in that position anymore? Great, I think he should. If he gets his feelings hurt because I’m not being super friendly about it? Well… okay. I’m not trying to be malicious about it or do anything other than clearly communicate the problem. But it seems like the lemmy.ml “in charge” crew in general has a lot of a mentality that’s kind of like, “Well, I’m in charge, and you’re not, so fuck what you think and fuck your rights. Ban.” (or whatever). The way I operate is that really makes me not want to be extra friendly or courteous to people. I used to have a regular donation to Lemmy development set up, I used to take it seriously the idea of getting involved in contributing to the code, and then I observed how they operate, and … like I say I’m mostly talking to the other people involved who I think should be aware of this. If the devs want to react, fix it, or get involved in the conversation, then sure, sounds good.

The fix is in the comments below, if someone else wants to contribute it and do the very small amount of work of getting it in.

*Quixote

The live docs at:

https://join-lemmy.org/docs/administration/install_docker.html

Link to:

https://raw.githubusercontent.com/LemmyNet/lemmy-docs/main/assets/docker-compose.yml

Which is what needs to be updated.

It’s present in the link on:

https://join-lemmy.org/docs/administration/install_docker.html

Which refers people to download:

https://raw.githubusercontent.com/LemmyNet/lemmy-docs/main/assets/docker-compose.yml

What you’re linking to is not what the live docs link to. I don’t know what main/docker is for, but the docs link to main/assets, not there.