DarkDarkHouse, For me it’s Pi-hole. For six months it runs fine, then dies so horribly I resort to snapshot rollback and we both pretend it never happened.
Mechanize, Give technitium a go, my woes diminished drastically with that.
thickconfusion, !RemindMe 7d
ayaya, Weird. I’ve had a Pi-Hole + Unbound running on a Pi Zero since 2018 and it’s never had any issues. I expected the Zero to kinda suck but it has been nothing but smooth sailing. It gets USB power from my router and even if my router reboots the Pi also auto reboots itself.
I do next to no maintenance on it and it just keeps on chugging along. Maybe once every six months or so I SSH in and do a
pihole -up
and that’s it.
NegativeLookBehind, I’m not self hosting an instance, but kbin is super fucking broken lately and it’s getting really frustrating. It’s been about a week. I submitted a ticket in their Git repo, but no response.
tal, The most-recent release of lemmy dicked up outbound federation pretty badly on the instance I use.
u_tamtam, Take that as you want but a vast majority of the complaints I hear about nextcloud are from people running it through docker.
xantoxis, Does that make it not a substantive complaint about nextcloud, if it can’t run well in docker?
I have a dozen apps all running perfectly happy in Docker, i don’t see why Nextcloud should get a pass for this
recapitated, I have only ever run nextcloud in docker. No idea what people are complaining about. I guess I’ll have to lurk more and find out.
u_tamtam, See my reply to a sibling post. Nextcloud can do a great many things, are your dozen other containers really comparable? Would throwing in another “heavy” container like Gitlab not also result in the same outcome?
recapitated, Things should not care or mostly even know if they’re being run in docker.
u_tamtam, Well, that is boldly assuming:
- that endlessly duplicating services across containers causes no overhead: you probably already have a SQL server, a Redis server, a PHP daemon, a Web server, … but a docker image doesn’t know, and indeed, doesn’t care about redundancy and wasting storage and memory
- that the sum of those individual components work as well and as efficiently as a single (highly-optimized) pooled instance: every service/database in its own container duplicates tight event loops, socket communications, JITs, caches, … instead of pooling it and optimizing globally for the whole server, wasting threads, causing CPU cache misses, missing optimization paths, and increasing CPU load in the process
- that those images are configured according to your actual end-users needs, and not to some packager’s conception of a “typical user”: do you do mailing? A/V calling? collaborative document editing? … Your container probably includes (and runs) those things, and more, whether you want it or not
- that those images are properly tuned for your hardware, by somehow betting on the packager to know in advance (and for every deployment) about your usable memory, storage layout, available cores/threads, baseline load and service prioritization
And this is even before assuming that docker abstractions are free (which they are not)
bdonvr, (edited ) Most containers don’t package DB servers, Precisely so you don’t have to run 10 different database servers. You can have one Postgres container or whatever. And if it’s a shitty container that DOES package the db, you can always make your own container.
that those images are configured according to your actual end-users needs, and not to some packager’s conception of a “typical user”: do you do mailing? A/V calling? collaborative document editing? … Your container probably includes (and runs) those things, and more, whether you want it or not
that those images are properly tuned for your hardware, by somehow betting on the packager to know in advance (and for every deployment) about your usable memory, storage layout, available cores/threads, baseline load and service prioritization
You can typically configure the software in a docker container just as much as you could if you installed it on your host OS… what are you on about? They’re not locked up little boxes. You can edit the config files, environment variables, whatever you want.
u_tamtam, Most containers don’t package DB programs. Precisely so you don’t have to run 10 different database programs. You can have one Postgres container or whatever.
Well, that’s not the case of the official Nextcloud image: hub.docker.com/_/nextcloud (it defaults to sqlite which might as well be the reason of so many complaints), and the point about services duplication still holds: github.com/docker-library/repo-info/…/nextcloud
You can typically configure the software in a docker container just as much as you could if you installed it on your host OS…
True, but how large do you estimate the intersection of “users using docker by default because it’s convenient” and “users using docker and having the knowledge and putting the effort to fine-tune each and every container, optimizing/rebuilding/recomposing images as needed”?
I’m not saying it’s not feasible, I’m saying that nextcloud’s packaging can be quite tricky due to the breadth of its scope, and by the time you’ve given yourself fair chances for success, you’ve already thrown away most of the convenience docker brings.
bdonvr, Docker containers should be MORE stable, if anything.
u_tamtam, and why would that be? More abstraction thrown in for the sake of sysadmin convenience doesn’t magically make things more efficient…
bdonvr, Nothing to do with efficiency, more because the containers are come with all dependencies at exactly the right version, tested together, in an environment configured by the container creator. It provides reproducibility. As long as you have the Docker daemon running fine on the host OS, you shouldn’t have any issues running the container. (You’ll still have to configure some things, of course)
nullpotential, The simple fix is to not use nextcloud
TBi, What’s the alternative?
riesendulli, Open media vault on pi4 is shitting the bed constantly
Bakkoda, My wonderful MongoDB powered, old as fuck mFi vm. It’s running on Ubuntu 14 because that’s the last supported version and Ubiquiti abandoned this shit decades ago. It’s set to restore and reboot once a month. That usually keeps shit working lol
possiblylinux127, Please tell me you don’t connect that to the internet
Bakkoda, (edited ) Haha fuck no.
EDIT: I kind of wish i had said yes just to spice things up.
fossilesque, I like to imagine it being pickled like Ozzy or Keith Richards.
Aurix, It is fine, but then again I update it often too late which is actually pretty bad. The problem is Nextcloud pushes new features and a high frequency schedule of releases with those at an alarming rate of speed. Perhaps for corporate environments it is not as big of a deal as a professional team can fix obscure bugs with their knowledge and experience on their mirrored test servers, but home users don’t have these resources available and public community knowledge and bug fixes need time which that release schedule hinders.
I still wouldn’t say it is bad by default, simply because somehow it runs pretty stable for me since a decade. Updates are a pain though with many breaking changes and little bugs.
AmosBurton, Thats unfortunate.
I had a vm (windows) on proxmox that was crashing ~5-10 times a week. Turned out to be a graphics settings that was killing it.
norgur, Yep. Got such a service as well. I’ve got this one docker container that’s supposed to connect to a VPN and provide access from the outside to another one. The bitch keeps just crashing to a point where even “restart policy: always” will give up on it. Doesn’t matter too much usually, since I can start the container before I need it, and it will usually run for half a day or so, yet still
rambos, Bad stories about nextcloud scare me 😂 I hope Im not gonna jinx myself, but my nextcloud runs super stable for almost a year. I get some errors while updating, but service doesnt stop working and its usually simple fix by following the message it shows.
I removed apps that I dont use (most of them) and web ui became super fast on my budget server
Actually all services are so smooth and almost no issues, maybe beginner luck 😉
virtueisdead, Invidious. It got so bad that I just gave up and switched to piped which has been… well, not perfect, but definitely far more consistent.
SomethingBurger, Paperless often randomly stops accepting new documents. I have to wait several hours or restart it.
possiblylinux127, (edited ) My Nextcloud has been flawless. The only issue I’ve had was NFS permissions. I have automatic update setup for docker so it stays up to date.
Care to share what broke?
ThePythonist95, Not using Nextcloud. Found it a bit difficult to deploy and maintain than OwnCloud. Since then, I haven‘t had any problems with OwnCloud.
callmepk, I don’t, I just keep running out of memory on my servers….
Add comment