3 ms·

This looks interesting but I'm clearly missing something. Could someone explain what does this terminal do for containers and flatpaks? Even reading the linked

by p4bl0 3y ago

This looks interesting but I'm clearly missing something. Could someone explain what does this terminal do for containers and flatpaks? Even reading the linked blog post didn't help me, probably because I only use containers a little and no flatpaks at all so I have no experience with what would make using them more confortable (if that is indeed the point?). Thanks! EDIT: Ah, looking at the screenshots on the project's page I see that it has a menu listing running containers which allows to directly open a terminal tab with a shell running inside the selected container. Is that it or is there more to it? What about flatpaks? Do flatpaks actually work like containers?

whilenot-dev 3y ago
> What about flatpaks? Do flatpaks actually work like containers? From what I found[0] Flatpak can run OCI images. [0]: https://docs.flatpak.org/en/latest/under-the-hood.html https://docs.flatpak.org/en/latest/under-the-hood.html
nolist_policy 3y ago
> What about flatpaks? Do flatpaks actually work like containers? No, the flatpak connection is that Prompt is designed from the beginning to run inside a flatpak.
Vinnl 3y ago
Where this gets most interesting is if you're running atomic distributions like Fedora Silverblue. The idea is that the OS itself is immutable, i.e. when you get an update, the OS files are replaced wholesale, and you can't modify them yourself. Applications are installed in a layer on top of that via Flatpaks, and if you need more advanced tooling that's hard to run in a Flatpak (e.g. software development tools), you run those in a container - typically a container per project, or at least per stack. The reason Prompt is interesting is that 1. I can install it as a Flatpak which, as mentioned, is pretty much a requirement for me to install anything (on top of providing sandboxing), and 2. it makes it easier to jump into one of my development containers, and to see which container I'm currently working in.
mikae1 3y ago
jcastro has a demo here: https://youtu.be/qeUH1_fFSUs https://youtu.be/qeUH1_fFSUs

by p4bl0 3y ago

whilenot-dev 3y ago

> What about flatpaks? Do flatpaks actually work like containers? From what I found[0] Flatpak can run OCI images. [0]: https://docs.flatpak.org/en/latest/under-the-hood.html https://docs.flatpak.org/en/latest/under-the-hood.html

nolist_policy 3y ago

> What about flatpaks? Do flatpaks actually work like containers? No, the flatpak connection is that Prompt is designed from the beginning to run inside a flatpak.

Vinnl 3y ago

Where this gets most interesting is if you're running atomic distributions like Fedora Silverblue. The idea is that the OS itself is immutable, i.e. when you get an update, the OS files are replaced wholesale, and you can't modify them yourself. Applications are installed in a layer on top of that via Flatpaks, and if you need more advanced tooling that's hard to run in a Flatpak (e.g. software development tools), you run those in a container - typically a container per project, or at least per stack. The reason Prompt is interesting is that 1. I can install it as a Flatpak which, as mentioned, is pretty much a requirement for me to install anything (on top of providing sandboxing), and 2. it makes it easier to jump into one of my development containers, and to see which container I'm currently working in.

mikae1 3y ago

jcastro has a demo here: https://youtu.be/qeUH1_fFSUs https://youtu.be/qeUH1_fFSUs