Cloudron base image 5

[timconsidine]

@girish said in Cloudron 8.3 + Base image 5.0.0:

I will update this post with the finalized base image 5.0.0 sha256 when it's tested across a large variety of apps.

Updated base image yet or that one still applicable ?

Asking because I was using it in docker builds fine, but suddenly apt stopped being accessible :

=> ERROR [ 3/14] RUN apt-get update && apt-get install -y --no-install-recommends gosu     && rm -rf /var/lib/apt/lists/*       1.1s
------                                                                                                                                
 > [ 3/14] RUN apt-get update && apt-get install -y --no-install-recommends gosu     && rm -rf /var/lib/apt/lists/*:                  
0.397 Get:1 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]                                                       
0.464 Get:2 http://archive.ubuntu.com/ubuntu noble InRelease [256 kB]                                                                 
0.582 Get:3 https://packages.redis.io/deb noble InRelease [3854 B]                                                                    
0.642 Err:3 https://packages.redis.io/deb noble InRelease                                                                             
0.642   At least one invalid signature was encountered.
0.715 Err:1 http://security.ubuntu.com/ubuntu noble-security InRelease
0.715   At least one invalid signature was encountered.
0.887 Err:2 http://archive.ubuntu.com/ubuntu noble InRelease
0.887   At least one invalid signature was encountered.
0.910 Get:4 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
0.984 Err:4 http://archive.ubuntu.com/ubuntu noble-updates InRelease
0.984   At least one invalid signature was encountered.
1.020 Get:5 http://archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
1.091 Err:5 http://archive.ubuntu.com/ubuntu noble-backports InRelease
1.091   At least one invalid signature was encountered.
1.097 Reading package lists...
1.111 W: GPG error: https://packages.redis.io/deb noble InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'https://packages.redis.io/deb noble InRelease' is not signed.
1.111 W: GPG error: http://security.ubuntu.com/ubuntu noble-security InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://security.ubuntu.com/ubuntu noble-security InRelease' is not signed.
1.111 W: GPG error: http://archive.ubuntu.com/ubuntu noble InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://archive.ubuntu.com/ubuntu noble InRelease' is not signed.
1.111 W: GPG error: http://archive.ubuntu.com/ubuntu noble-updates InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://archive.ubuntu.com/ubuntu noble-updates InRelease' is not signed.
1.111 W: GPG error: http://archive.ubuntu.com/ubuntu noble-backports InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://archive.ubuntu.com/ubuntu noble-backports InRelease' is not signed.

Been a problem for couple of hours

[timconsidine]

Weird
Got bored and grasping at straws so did docker system prune -a --volumes -f
Now it’s building again and apt-get succeeds.

Sometimes I doubt my connection with reality

[girish]

The error indicates maybe a network error (or maybe ran out of disk space?)

[timconsidine]

@girish that’s what I thought initially, but I checked both of those and was able to carry on working other prjects while waiting.
I don’t understand it, and can only put it down to a docker weirdness.
After a while I noticed that local docker desktop was asking to update, and after that I cleared the docker environment.
Then all is back to normal (whatever that is).
Phew