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.
How so? if I compromise a containerized app I get all the data that app has access to.
From a security standpoint, each and every container running actually increases the potential attack surface.
The attack surface yes, but not the attack volume. No matter if the app is containerized or native, it has access to the data that it has to operate to. That’s literally part of computer nature.
But a containerized app, assuming the container service itself is kept up to date, has less hooks to break into other stuff than a native app does. For starters, a native app can read everything that’s world-readable, which in a shared system might be lots of stuff but in a containerized app might be quite minimal.
- 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 #0
Thanks for the issue… looks like codeberg pages service is down :(
