Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Next evolution, just a one line bash script.
For me it's more like new interesting self hosted project and then find out it's only distributed as a docker container without any proper packaging. As someone who runs FreeBSD, this is a frustration I've run into with quite a number of projects.
It’s because I’ve seen What people can do with a simple docker container that I completely agree. It’s too nice to go back.
I'd agree more if most docker stuff didn't depend on running as root.
I think your looking for podman
yeha, but the big projects like linuxserver.io love creating docker images with root access, even if people have warned them it is an awful security practice. I rewrote all of their images in a personal repo, screw that. I won't run shit as root in my machine, even in containers.
There's rootless docker, or podman, or numerous other container runtimes. The beauty in containers is separating concerns. How you choose to run it, root or rootless, is up to you in all but the nichest of scenarios.
I'm the opposite because I've had nothing but bad luck with docker. I should really spend more time with it but ugh
What's wrong with it
It's definitely worth learning. I had the damnedest time with docker until I went to a meetup and had someone ELI5 to me. And it wasn't that I wasn't technical. I just couldn't wrap my head around so many layers of extraction.
The guy was very patient with me and helped me get started with docker compose and the rest is history.
I was so surprised by how easy it was to install Yacy--I'd thought a self-hosted search engine would be tough, but I made a docker-compose file and pointed my reverse proxy to the server, works perfectly so far!
Me: install it, doesn't work, read the docs, screw with all the missing things, doesn't work, read the forms, install something else I missed, doesn't work, find more forums, find the right answer, patch it up, get it working, figure out that the application is slow, missing critical features, and really just doesn't do what I needed to do.
really just doesn’t do what I needed to do.
This has been my experience, or sort of does what I want it to do, but I have to rethink what I need it to do instead of something really simple. Like a "new type of shared file system" that replaces NFS/Windows sharing. So instead of files in a standard file system one can manage with a file browser, it has "indexed" your files in such a way that the actual files are renamed into data chunks, and one "finds" files by their non-intuitive search engine that can't do even basic search engine tricks like "AND/OR" searches, wildcards, and the results are hit and miss. "But it's faster and more elegant!" So how do you restore from backup when the system fails? "When the system does whatnow?"
Yeah, no thanks. I can recover files from a file system much easier than some proprietary encoded bullshit fronted with a bad search engine over a proprietary and buggy index.
I asked the other week if anyone made a system that left files alone and just indexed them and gave you a place to store meta without moving them. Options do seem to exist, but they need LOTS of extra work
Or it does work, and then I never actually end up using it again.
And then months later I'll have to do something similar and I've forgotten I even installed something that can do that, so I install another related thing.
I believe this to be true for nearly all products. It has to be super simple to test, because you need to assess if it fits your needs. The mental model for a priori assessment is not strong enough usually.