kcgodwins

Just made the switch myself but haven't yet run NG; will look into doing so when time permits.

Going to ignore this "error" in FCP for now. I'm on 6.12.15 at the moment, which mitigates the known vulnerabilities from what I've read. This "patch" process seems way too "knee jerk" for me so I'm going to sit back and monitor, which falls in line with what I do regarding new releases and such (i.e. I'm not an early/first day adopter). Thanks for the efforts, nonetheless. As this matures, I will likely embrace it.

I'm having similar issues with permissions but for different reasons (which are irrelevant so I'll spare you the screen space). I started looking at the docker docs for this app and it appears that there is no mechanism for specifying the user and group to store the files as, so it defaults to root/root. It'd be really marvelous if this could be added (or, if it's there somewhere, I could be pointed to the info documenting it). Thanks again!

My only non-monetary concern relative to this is maintaining backwards compatibility in apps/plugins going forward, since obviously this new situation is going to introduce a scenario where some people are not going to want to upgrade due to the additional cost. Case in point -- I'm currently running 6.11.5; I'm planning to upgrade to 6.12.x at some point relatively soon but still haven't gotten there due to a number of reasons. That said, the minimum requirement for the Community Applications plugin is 6.12.x as of November of last year. This means I've stopped applying CA upgrades to my system until I get to 6.12. I'm grandfathered (allegedly (lol)) so it's not going to be an issue for me but it may be an issue for someone new to the platform down the road. I'm a grateful user of all these apps and I know very little about what goes into making them all mesh together, so I'm not sure if maintaining backward compatibility is even a reasonable ask, but figured I'd at least point it out. Cheers.

Doesn't show up for me in Community Apps. I'm running 6.9.2.

It was line 424 for v6.9.2; updated it and worked great. Thanks all.

Thanks, I'll take a look at it. Do you (or anyone) know why this has become an issue all of a sudden? Just curious. Thanks again. Mike

Could you post what line 448 looks like prior to the above update? I'm running 6.9.2 and I'm wanting to make sure I'm touching the correct line. My current line 448 reads: $reply_json = json_decode($reply, true); Seems like a really radical update if that's what I'm supposed to be replacing. More and more of my dockers have gone "not available" in the past week, for reasons I'm unaware of. I'm hoping that this might fix it. TIA ETA: I'm also not opposed to upgrading to 6.10 or 6.11 if one or the other will resolve this. Thx again.

You're right, it's right there. Not sure how I overlooked it but thanks for the pointer.

Hi; is there a cookbook for upgrading ownCloud in this docker? I read some time ago that the gui-based upgrade doesn't work (unfortunately, I read that after I tried it LOL), so I guess I'm doing it manually. I don't mind digging around and compiling the info I need to get it upgraded but if someone who has already done this a time or two has a guide somewhere I'd rather not re-invent the wheel. Thanks in advance and thank you for all the efforts on this and all dockers. You guys are wizards...

Cool, thanks. Learn something new every day. 🙂

I'd like an answer for this question as it relates to the java version if there's a viable answer for it. I don't necessarily want to upgrade minecraft versions as they are released (right now I'm running 1.18.2 and didn't want to go to 1.19 right away; however, looks like the docker decided to upgrade to 1.19 on its own anyway). Thanks in advance.

I'm usually pretty keen on figuring out the simplest of things (which I think this should be one) but, alas, here I am to ask... How can I determine which version of Uptime Kuma I'm running? Normally I'd console into the docker, do a ps -aux to find the executable and then do something like <executable name> -v However, this container has no ps, so I'm scratching my head. Thanks in advance.

Oops, I had forgotten I'd already asked. How embarrassing. Thanks for the info.

Hello everyone. I switched from Nextcloud to Owncloud relatively recently (approximately a month or 2 ago) and I very much like it, but there's an issue I'm seeing that's troubling me somewhat and I wanted to see if it's just happening to me, or if this is expected behavior. Seems that, each time I restart the OC docker, it spends considerable time essentially rebuilding itself; downloading packages and whatnot. Is this the way it's designed to function? It seems odd to me, and it's the only one of my approximately dozen dockers that behaves this way. Just thought I'd ask. Thanks.