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.
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.
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.
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
When the project installation steps start with a 'git clone'.
Nah, to much work, use curl to download a script and blindly run it...
I'm the opposite because I've had nothing but bad luck with docker. I should really spend more time with it but ugh
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.
Abstraction?
I'm like that. It feels like a total waste of resources, and introduces unneeded complexity for backup, updates, file access, networking and general maintenance.
I would take a deb repo over docker any day of the week.
I was blown away how a relatively unknown project like immich provides one Docker compose file to bring up a whole self-hosted ~~Google photos~~ photo management suite, complete with tagging, mapping, transcoding and semantic search. Local, offline semantic search.
I got into the idea of selfhosting my photos, and wanted facial recognition to search them. I also wanted a selfhosted chat server. Nextcloud came as the obvious choice that did both. After days of tinkering and fixing errors in the log one by one, everything worked except the facial recognition which said everything was fine but the faces just didn't get recognised. Also the mobile experience for Memories wasn't the best. Then luckily I came across immich and it was up and running in about 5-6 mins of configuration max, and it has better facial recognition than the main big commercial option. Insane. For chat I got a synapse server with coturn which also took about 15 mins of docker composing and setting configurations/accounts to my liking.
(I still think Nextcloud is cool but it's overkill and loaded with too many features I don't need + installation is a task & documentation/online support communities are scattered between the various methods of installation)
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.
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.
This oh my God. Just the other day I tried to install a project off git, it had a nice little .bat file to install all the requirements except half if them just didn't exist or were so niche I couldn't find anything on them after searching. Would love more dockers please.
.bat?
*starts loading shotgun.
Surely you mean .sh, right?
Ah well, maybe he used to much aliases? starts sweating in penguin costume
Naw they only had windows projects. I run all my stuff through VMware. Gotta have windows for stupid easy anti-cheat. Trust me I only use it when I have to, please put the gun down mr railcar!
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.
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.
As someone that uses FreeBSD as its main server, it's kinda the other way around haha
Masochist
Building a docker container isn't normally to hard. I usually will create a PR with a dockerfile and docker compose
As a NixOS user, I pick whatever is supported well as a NixOS package.