toolbox-vscode
distrobox
toolbox-vscode | distrobox | |
---|---|---|
20 | 403 | |
277 | 8,976 | |
- | - | |
0.0 | 9.6 | |
10 months ago | 7 days ago | |
Shell | Shell | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
toolbox-vscode
-
Fedora Silverblue and development environments
This helper script
- Considering switch to Silverblue, sanity check, please?
-
Devs using SilverBlue, how to use your IDE?
VSCode + toolbox container + https://github.com/owtaylor/toolbox-vscode.git
-
Best practices for Silverblue containers ?
Linking VS code with remote development in your container can be achieved very well. I found this repository and the setup is superb! https://github.com/owtaylor/toolbox-vscode
-
toolbox / podman integration with vscode
Have a look at this script, which has been made even easier with this.
-
How to work with editors?
I use https://github.com/owtaylor/toolbox-vscode, then you can have the vscode frontend in flatpak and the backend (where language servers and compilers run) in a toolbox container
-
Best approach for doing development in Fedora Silverblue?
There’s this script, and also this approach to simplify using said script.
- 30 days of silver blue 🌟
-
Integration of Toolbox And Flatpak In Silverblue
Yes sir, you need to use the Remote - Containers extension and this script https://github.com/owtaylor/toolbox-vscode
-
Vscodium
You can use toolbox-vscode to make the flatpak more useful
distrobox
-
Show HN: Convert your Containerfile to a bootable OS
That seems more like Distrobox to me(?) https://distrobox.it/
-
Windows 11 now comes with its own adware
Regarding the stability issue on a dev machine - you may be interested in playing with one of the immutable-os distros, such as SilverBlue (fedora based).
The high-level take-away is you can't break your actual OS since it's root filesystem is read-only, and you use "pet" containers (on docker, podman, whatever) to do your work in. Applications are either sandboxed via Flatpak, or installed/run inside your pet containers. If your pet container dies, you cry about it for a moment, and when you're ready you get a new one - your actual os and other containers remain unaffected.
I use distrobox[1] to create/run the pet containers.
[1] https://github.com/89luca89/distrobox
-
Tools for Linux Distro Hoppers
Distrobox is a tool that enables us to try Linux distro CLI, including their package manager. This requires a containerization tool (e.g., Docker). In Windows, this can be achieved using WSL (Windows Subsystem for Linux)
- Distrobox: Use any Linux distribution inside your terminal
-
Fedora Atomic Desktops
I use containerized versions of things, ubuntu and chainguard images mostly.
You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Raspberry Pi is manufacturing 70K Raspberry Pi 5s per week
https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Operating System?
Yes, you can do that but I've seen others use something like distrobox to run linux inside of SteamOS: https://github.com/89luca89/distrobox/blob/main/docs/posts/steamdeck_guide.md
-
How much will I screw up my system after installing Merkuro Calendar (KDE Akonadi application), formerly called Kalendar, on GNOME?
For such cases you might use something like this: https://github.com/89luca89/distrobox
-
Battery consumption of using remote development with WSL2?
Btw #3: Depending on what the user is trying to accomplish, e.g. maybe to make WSL(2) itself more of a "subsystem" than a "container engine", using something like Distrobox or nsbox.dev can be a good idea (along with Docker or Podman in Distrobox's case; the other one uses systemd-nspawn).
-
Cannot run containers with Distrobox
1. Find here in "Containers Distros" section the distro image that you want to install ("Toolbox" versions are better because they are configured for Distrobox) and get it URL: https://distrobox.it/compatibility/#containers-distros 2. Use that URL to create Distrobox: distrobox create -i registry.fedoraproject.org/fedora-toolbox:39 -n fedora_1_39 3. Enter Distrobox fedora_1_39: distrobox enter fedora_1_39 4. You are already in Distrobox console. Look at the name in console, it should be include the container name. 5. To exit Distrobox: exit 6. If you run: distrobox list you will see all distroboxes on the system. You will also see that distrobox that we exited is still running. 7. To stop distrobox use commands: distrobox stop fedora_1_39
What are some alternatives?
kinto - Mac-style shortcut keys for Linux & Windows.
toolbox - Tool for interactive command line environments on Linux
extension-manager - A utility for browsing and installing GNOME Shell Extensions.
wsl-distrod - Distrod is a meta-distro for WSL 2 which installs Ubuntu, Arch, Debian, Gentoo, etc. with systemd in a minute for you. Distrod also has built-in auto-start feature on Windows startup and port forwarding ability.
keepassxc - KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
docker-android - Android in docker solution with noVNC supported and video recording
sorun - Desktop Linux for Creators
flatpak - Linux application sandboxing and distribution framework
manjarno - Reasons for which I don't use Manjaro anymore
rustdesk - An open-source remote desktop, and alternative to TeamViewer.
ydotool - Generic command-line automation tool (no X!)
nix - Nix, the purely functional package manager