npub1l3gpk6vrudg8r67swqlex5alv9ch59s4lw46kk6hekuxe2n3aczsyqvu48 (npub1l3g…vu48)
To add, and address a separate point:
you're trusting them to not only update their app in the container image, but every underlying utility and library used.
Most projects that I can think of, building container images usually is part of the CI/CD pipeline, and those images usually start their build with a number of apt / dnf / yum / apk / pkg / etc. invocations to pull the libs, meaning that every application update is, within a day or two, an image update, and usually a library update since it's in effect firing up a very lightweight VM, running a bunch of package installations, and then copying its own files in.
Some places even build the app in the container with the libraries to make sure it's all set up correctly for the environment, and then have a second build stage, so you're not holding all the build-time dev dependencies that it needs, but that's getting a bit besides the point.
npub1trdnqrfstufc45awha43p6xy2n0v6czuhapzh4r09hap08dg0c6s9gussx (npub1trd…ussx)
Teknikal_Domain /
npub1nr…ezxf2
2023-08-06 07:08:40
in reply to nevent1q…myyr
Author Public Key
npub1nray8pxrwrrpv5yljpyjj4r6cmp4pcqwqhrrc7kuw8dtvqdaekrsnezxf2Published at
2023-08-06 07:08:40Event JSON
{
"id": "d201ea51158c6002e853f7d1cb19babfdd43958345de685ef19c4838876648b9",
"pubkey": "98fa4384c370c616509f904929547ac6c350e00e05c63c7adc71dab601bdcd87",
"created_at": 1691305720,
"kind": 1,
"tags": [
[
"p",
"fc501b6983e35071ebd0703f9353bf61717a1615fbabab5b57cdb86caa71ee05",
"wss://relay.mostr.pub"
],
[
"p",
"58db300d305f138ad3aebf6b10e8c454decd605cbf422bd46f2dfa179da87e35",
"wss://relay.mostr.pub"
],
[
"p",
"c95a71dfb95245bfb233a5ccea6dbcb03adda051221413144a54a206165aa52f",
"wss://relay.mostr.pub"
],
[
"p",
"0b9db3c0a234209dc7a0645154b009b96c8f8fdadd0558d704dcb85404b2bb9c",
"wss://relay.mostr.pub"
],
[
"e",
"9ba798499a542a816f9cf30bc2504acd9b381a4ca6480c0875282f364bbd9bcb",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.tekdmn.me/users/tek_dmn/statuses/110841411720729330",
"activitypub"
]
],
"content": "nostr:npub1l3gpk6vrudg8r67swqlex5alv9ch59s4lw46kk6hekuxe2n3aczsyqvu48 \n\nTo add, and address a separate point:\n\nyou're trusting them to not only update their app in the container image, but every underlying utility and library used.\n\nMost projects that I can think of, building container images usually is part of the CI/CD pipeline, and those images usually start their build with a number of apt / dnf / yum / apk / pkg / etc. invocations to pull the libs, meaning that every application update is, within a day or two, an image update, and usually a library update since it's in effect firing up a very lightweight VM, running a bunch of package installations, and then copying its own files in.\n\nSome places even build the app in the container with the libraries to make sure it's all set up correctly for the environment, and then have a second build stage, so you're not holding all the build-time dev dependencies that it needs, but that's getting a bit besides the point.\n\nnostr:npub1trdnqrfstufc45awha43p6xy2n0v6czuhapzh4r09hap08dg0c6s9gussx",
"sig": "8aebf7227d8ed8f72f443cc77af090eb2c5b654abdef7ca33c2a24d511c180a5d8e920c05db71fe2bf714ddde18702103f664d2b4cdde5fed3fb10d9ea4a735c"
}