Not much of a take here mate. Looks more like blog spam, and your blog entry isn't even complete.
okay thank you
Keeping containers up to date for security and bugfixes is just as important as OS packages.
yeah, but any update failure of a container is less fatal. and only affects the isolated service.. it's way easy to manage this situation than an unbootable server.
But that's very hypothetical. I've been running servers for more than a decade now and never ever had an unbootable server. Because that's super unlikely. The services are contained in to several user accounts and they launch on top of the operating system. If they fail, that's not really any issue for the server booting. In fact the webserver or any service shouldn't even have permission to mess with the system. It'll just give you a red line in systemctl and not start the service. And the package managers are very robust. You might end up with some conflicts if you really mess up and do silly things. But with most if them the system will still boot.
So containers are useful and have their benefits. But I think this is a non-issue.
* Host simplycreate.online:443 was resolved. * IPv6: 2a0a:4580:103f:c0de::2 * IPv4: 217.197.84.141 * Trying [2a0a:4580:103f:c0de::2]:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [512 bytes data] * CAfile: /data/data/com.termux/files/usr/etc/tls/cert.pem * CApath: /data/data/com.termux/files/usr/etc/tls/certs * TLS connect error: error:00000000:lib(0)::reason(0) * OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to simplycreate.online:443 * closing connection #0Thanks for the issue... looks like codeberg pages service is down :(
