This issue is already quite widely publicized and quite frankly “we’re handling it and removing this” is a much more harmful response than I would hope to see. Especially as the admins of that instance have not yet upgraded the frontend version to apply the urgent fix.

It’s not like this was a confidential bug fix, this is a zero day being actively exploited. Please be more cooperative and open regarding these issues in your own administration if you’re hosting an instance. 🙏

You are viewing a single thread.
View all comments
7 points

unfortunately there’s no images for 0.18.2-anything yet :(

permalink
report
reply
20 points
*

There are, via dessalines’ repo. It’s for lemmy-ui only, at 0.18.2-rc.1.

I have it running already on my instance, and have for 93min now.

permalink
report
parent
reply
2 points

thanks, I guess I missed it. gonna update ASAP just in case, even though I’m the only user of my instance.

permalink
report
parent
reply
9 points

Yes, there is: 0.18.2-rc.1, which has the hot fix.

permalink
report
parent
reply
1 point

Excuse my ignorance, but where can I find details to this issueand does it affect only 0.18.1, or also 0.18.0?

permalink
report
parent
reply
3 points

For amd64, Lemmy dev Dessalines pushes images to his Docker Hub repo usually right after a new version comes out.

Since they don’t release arm64 builds anymore, I build them regularly and push them to my repo, which can be found here.

permalink
report
parent
reply
2 points
*

Multi-platform images are kept up-to-date on this 3rd party repo: https://github.com/ubergeek77/lemmy-docker-multiarch

permalink
report
parent
reply
-24 points

Which leads me to ask: why are we still using Docker images as a MAJOR part of our infrastructure when superior alternatives exist? The Docker aspect made me realize how hacked together the codebase actually is.

permalink
report
parent
reply
11 points

Just because it’s not using your personal preference of containerization doesn’t qualify it as being “hacked together”. Docker is a perfectly acceptable solution for what Lemmy is.

permalink
report
parent
reply
-9 points

That’s just like your opinion, man.

permalink
report
parent
reply
9 points

I will always espouse containers for critical workloads as they provide much better orchestration, especially during deployment. If your complaint is specifically against docker, I agree, we should be using k8s

permalink
report
parent
reply
-5 points

I disagree.

IMO, we should be using Nix and OCI.

permalink
report
parent
reply
8 points

What are these ‘superior’ alternatives?

permalink
report
parent
reply
6 points

That’s a ridiculous take

permalink
report
parent
reply
1 point

What’s so bad about using docker? Serious question.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.1K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments