Issue pulling custom app from registry on the same cloudron

[james]

Hello @vk182
Great to read!

[mathieuepitech]

@james Unfortunately on my side it didn't works.
Now the command cloudron-support --troubleshoot get 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]

Hello @mathieuepitech

Can you please run the following commands:

# first one
curl 127.0.0.1
# second one
curl 127.0.0.1

If the second curl fails there is still a networking issue.

[mathieuepitech]

@james I get an HTML page with Cloudron - Not Found error on both curl

[james]

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?

[mathieuepitech]

@james said:

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 !

[james]

Hello @mathieuepitech
Glad to read that.
So it was indeed also the Ubuntu Kernel 110 issue.

[timconsidine]

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.

[james]

Hello @timconsidine

@timconsidine said:

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?

@timconsidine said:

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?

[timconsidine]

@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.