Issue pulling custom app from registry on the same cloudron
-
Hello @mathieuepitech
Can you give me the output of the following command on your system?uname -narWe found systems with kernel version <
110are not effected. -
Hello @mathieuepitech
Can you also try to apply this patch https://git.cloudron.io/platform/box/-/commit/bffc97ab2fedb06100bc507abd0f8b42d343ea6e
and restart the cloudron-firewall service with:systemctl restart cloudron-firewall.service -
Hello @mathieuepitech
Can you also try to apply this patch https://git.cloudron.io/platform/box/-/commit/bffc97ab2fedb06100bc507abd0f8b42d343ea6e
and restart the cloudron-firewall service with:systemctl restart cloudron-firewall.service -
Hello @mathieuepitech
Can you also try to apply this patch https://git.cloudron.io/platform/box/-/commit/bffc97ab2fedb06100bc507abd0f8b42d343ea6e
and restart the cloudron-firewall service with:systemctl restart cloudron-firewall.service@james Unfortunately on my side it didn't works.
Now the commandcloudron-support --troubleshootget everything ok.
But I still cannot update my custom app from an image that is stored in a custom registry on the same cloudron server.I even try to reboot my server and that didn't change anything.
-
@james Unfortunately on my side it didn't works.
Now the commandcloudron-support --troubleshootget everything ok.
But I still cannot update my custom app from an image that is stored in a custom registry on the same cloudron server.I even try to reboot my server and that didn't change anything.
-
Hello @mathieuepitech
Can you please run the following commands:
# first one curl 127.0.0.1 # second one curl 127.0.0.1If the second curl fails there is still a networking issue.
-
@james I get an HTML page with
Cloudron - Not Founderror on both curl -
Hello @mathieuepitech
Okay, so the network issue is resolved by the applied patch.
When you configure your docker registry in the Cloudron Dashboard, is there any error when saving?Hello @mathieuepitech
Okay, so the network issue is resolved by the applied patch.
When you configure your docker registry in the Cloudron Dashboard, is there any error when saving?My bad, with the issue, I had remove the registry and couldn't add it back.
Now I have added back and it's working perfectly.Thank you very much !
-
J joseph has marked this topic as solved on
-
FWIW. I have just run into the issue.
Broke connectivity to my cloudron-installed forgejo
Fixed using the patch after losing 4 hours to checking it was not something I did.IMHO :
- EITHER 9.1.6.should be pulled
- OR 9.1.7 should be accelerated
- AND some kind of a clearer higher profile URGENT ADVISORY should be issued for people to check if uname shows 110
I may have missed such an announcement, but I assume this affects quite a number of Cloudron users, so it should be addressed.
Probably a stupid perception issue but backups on patched 9.1.6 seem slower. Working but much slower than before. Will keep an eye on it and try to get some metrics (to rule out user perception).
Seems that rysnc location (hetzner Storage Box) needed remounting. No idea why, but seeks ok now. Watching.Indie app dev, scratching my itches, lover of Cloudron PaaS, communityapps.appx.uk
-
FWIW. I have just run into the issue.
Broke connectivity to my cloudron-installed forgejo
Fixed using the patch after losing 4 hours to checking it was not something I did.IMHO :
- EITHER 9.1.6.should be pulled
- OR 9.1.7 should be accelerated
- AND some kind of a clearer higher profile URGENT ADVISORY should be issued for people to check if uname shows 110
I may have missed such an announcement, but I assume this affects quite a number of Cloudron users, so it should be addressed.
Probably a stupid perception issue but backups on patched 9.1.6 seem slower. Working but much slower than before. Will keep an eye on it and try to get some metrics (to rule out user perception).
Seems that rysnc location (hetzner Storage Box) needed remounting. No idea why, but seeks ok now. Watching.Hello @timconsidine
OR 9.1.7 should be accelerated
Cloudron version 9.1.7 is already out and you should be able to update your system.
Is it not possible for you?EITHER 9.1.6.should be pulled
Why?
Since this is not a Cloudron issue in a general sense but a kernel issue, why 'revoke' Cloudron version 9.1.6? -
Hello @timconsidine
OR 9.1.7 should be accelerated
Cloudron version 9.1.7 is already out and you should be able to update your system.
Is it not possible for you?EITHER 9.1.6.should be pulled
Why?
Since this is not a Cloudron issue in a general sense but a kernel issue, why 'revoke' Cloudron version 9.1.6?@james good points, thank you.
Honestly … I didn’t check for 9.1.7, lost too much time getting stable operations again, didn’t want to risk further. I will get brave and do it when a process slot appears.
Revoke 9.1.6 : Yes, maybe knee-jerk overkill, but it’s undeniably broken (not Cloudron fault I accept) in a fairly fundamental way for a possibly/probably large number of users. However if 9.1.7 is out and reliable, then users have a path forward. If they know about it.
That’s where the Urgent Advisory Notice is relevant : please check if you’re on kernel xxxx, we have detected incompatibility of 9.1.6 with that, you can fix by 9.1.7 which is available now.
I didn’t choose to deploy 9.1.6, it happened on a reboot and I was left with a broken system. An Advisory would have shortened restoration of full functionality.
Indie app dev, scratching my itches, lover of Cloudron PaaS, communityapps.appx.uk
-
@james good points, thank you.
Honestly … I didn’t check for 9.1.7, lost too much time getting stable operations again, didn’t want to risk further. I will get brave and do it when a process slot appears.
Revoke 9.1.6 : Yes, maybe knee-jerk overkill, but it’s undeniably broken (not Cloudron fault I accept) in a fairly fundamental way for a possibly/probably large number of users. However if 9.1.7 is out and reliable, then users have a path forward. If they know about it.
That’s where the Urgent Advisory Notice is relevant : please check if you’re on kernel xxxx, we have detected incompatibility of 9.1.6 with that, you can fix by 9.1.7 which is available now.
I didn’t choose to deploy 9.1.6, it happened on a reboot and I was left with a broken system. An Advisory would have shortened restoration of full functionality.
Hello @timconsidine
we have detected incompatibility of 9.1.6
It is not only Cloudron version 9.1.6. It is every Cloudron version dating back almost 2 years with this specific kernel regression.
This issue does not arise due to the Cloudron update, but through the unattended-updates that update the kernel.
Also, this does not affect every Cloudron user since if you are still on Ubuntu 22, you will not even get that kernel version from unattended-updates afaik.That is why:
I didn’t choose to deploy 9.1.6, it happened on a reboot and I was left with a broken system.
happened.
That’s where the Urgent Advisory Notice is relevant : please check if you’re on kernel xxxx, we have detected incompatibility of 9.1.6 with that, you can fix by 9.1.7 which is available now.
I think we could do an announcement in the forum, that is a good idea.
-
J james referenced this topic on
-
Hello @timconsidine
I have posted the announcement here: https://forum.cloudron.io/topic/15442/ubuntu-24.04-kernel-6.8.0-110-regression-affecting-cloudron
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login