npub1trdnqrfstufc45awha43p6xy2n0v6czuhapzh4r09hap08dg0c6s9gussx (npub1trd…ussx) npub1l3gpk6vrudg8r67swqlex5alv9ch59s4lw46kk6hekuxe2n3aczsyqvu48 (npub1l3g…vu48) Personally I think FlatPak makes more sense, I don't think AppImage has the same sort of sandboxing which is the entire point of containers.
Unfortunately this comparison breaks down when you consider that Docker expects a sort of one-container-per-app topology, using stacks to link everything up. So a single application can be made of half a dozen containers, one for the app, one for the database, one for the frontend... All communicating on a loopback bridge network together. Updating these can be fun sometimes.
Also your understanding is good but misses some details, Docker (and the ContainerD runtime and system it uses) is doing basically all the work, the OS isn't doing anything besides cgroup separation. (And don't get me started on how Docker does storage and filesystems)
Teknikal_Domain /
npub1nr…ezxf2
2023-08-06 15:35:12
in reply to nevent1q…57x7
Author Public Key
npub1nray8pxrwrrpv5yljpyjj4r6cmp4pcqwqhrrc7kuw8dtvqdaekrsnezxf2Published at
2023-08-06 15:35:12Event JSON
{
"id": "0d2529412cd0a107cafaa8cb6157c0ad78d78015c50ce30d4137bedd89d2547d",
"pubkey": "98fa4384c370c616509f904929547ac6c350e00e05c63c7adc71dab601bdcd87",
"created_at": 1691336112,
"kind": 1,
"tags": [
[
"p",
"58db300d305f138ad3aebf6b10e8c454decd605cbf422bd46f2dfa179da87e35",
"wss://relay.mostr.pub"
],
[
"p",
"fc501b6983e35071ebd0703f9353bf61717a1615fbabab5b57cdb86caa71ee05",
"wss://relay.mostr.pub"
],
[
"p",
"0b9db3c0a234209dc7a0645154b009b96c8f8fdadd0558d704dcb85404b2bb9c",
"wss://relay.mostr.pub"
],
[
"p",
"c95a71dfb95245bfb233a5ccea6dbcb03adda051221413144a54a206165aa52f",
"wss://relay.mostr.pub"
],
[
"e",
"d3dd704a8fa700d164f3045a6189c2db99fa5b74b656780a920821fa57c1d8de",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.tekdmn.me/users/tek_dmn/statuses/110843403462733144",
"activitypub"
]
],
"content": "nostr:npub1trdnqrfstufc45awha43p6xy2n0v6czuhapzh4r09hap08dg0c6s9gussx nostr:npub1l3gpk6vrudg8r67swqlex5alv9ch59s4lw46kk6hekuxe2n3aczsyqvu48 Personally I think FlatPak makes more sense, I don't think AppImage has the same sort of sandboxing which is the entire point of containers.\n\nUnfortunately this comparison breaks down when you consider that Docker expects a sort of one-container-per-app topology, using stacks to link everything up. So a single application can be made of half a dozen containers, one for the app, one for the database, one for the frontend... All communicating on a loopback bridge network together. Updating these can be fun sometimes.\n\nAlso your understanding is good but misses some details, Docker (and the ContainerD runtime and system it uses) is doing basically all the work, the OS isn't doing anything besides cgroup separation. (And don't get me started on how Docker does storage and filesystems)",
"sig": "08c0b77701cd9f4851e5ae43ddc4ce483a10530fcddfa49fa9eee170a852630df8f4c32e9aff129a853cbc29eea7d7dd3b78a8182815d4a95531e1506dda5e29"
}