WSL
garden
Our great sponsors
WSL | garden | |
---|---|---|
406 | 40 | |
16,524 | 3,210 | |
1.3% | 2.9% | |
8.3 | 9.9 | |
6 days ago | 8 days ago | |
PowerShell | TypeScript | |
MIT License | Mozilla Public License 2.0 |
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.
WSL
-
GoboLinux
It absolutely 100% can be true.
As an example: Windows Services for Linux 2 used a special init daemon to interact with the host OS.
That meant no systemd. That meant that the `systemctl` program wasn't there.
This baffled legions, armies, of wannabe sysadmins.
https://stackoverflow.com/questions/55579342/why-systemd-is-...
https://superuser.com/questions/1785697/systemd-in-wsl-on-wi...
https://github.com/microsoft/WSL/issues/9477
https://askubuntu.com/questions/1132230/unable-to-run-any-sy...
People on the whole have no idea how this stuff works, and they just copy magic incantations from StackOverflow to get stuff to happen. If that doesn't work, then this OS is broken. The end.
For these guys, WSL was broken.
Result:
MS hired Lennart Poettering.
https://www.theregister.com/2022/07/07/lennart_poettering_re...
He "fixed" it. Systemd now works in WSL2. All those guides for noobs now work. Everyone is happy.
In a world where tools like Flatpak and Snap are proliferating and it's driving deep divisions between Linux distros, if you think the average person struggling with Linux is going to use `ldd` to work out where the dependencies for something live, I'm afraid you are a deep guru who lives on a different plane of existence.
We now have widely-used packaging systems which simply embed an apps entire dependency tree into a package to avoid people having to work out the difference between `apt` and `rpm`. Thousands of terabytes of disk are being burned to make this stuff go away.
Yes, this is too hard. Way too hard.
-
RamRamRamEveryoneSleepingOnDocker
One of the bugs where on the Docker side. As I have said, there have been several since release with a lot of impact period overlap. The latest and greatest is not resolved.
the issue you're descibing is a bug in at least 1 specific version of docker desktop, not wsl.
- Supercharge your Windows Development: The Ultimate Guide to WSL 🚀📟
-
Enabling IPv6 support for IPv4-only apps on Linux
The prerelease finally supports ipv6: https://github.com/microsoft/WSL/releases
-
Windows Subsystem for Linux 2.0 release
I think it's this bug https://github.com/microsoft/WSL/issues/8696
A real nightmare.
There are several issues in the repo related this bug, here's another one with over 500 comments:
https://github.com/microsoft/WSL/issues/6982
Almost 1000 total comments between both of these and basically no acknowledgement from microsoft.
- Why does "sudo apt reinstall bash" cause dpkg i/o error on WSL1?
-
WSL2 on Windows 11 - Virtual Disk vhdx is 200GB now , Inside Debian there is hardly few python codes. Is it due to this /mnt (these are windows drives mounted automatically by debian wsl)
It's been an open issue for years : https://github.com/microsoft/WSL/issues/4699
garden
-
Streamlining CI/CD Pipelines with Code: A Developer's Guide
To add to what's already been said: If you think about it, CI pipelines are typically a complete description of how your system is built, tested, and deployed.
Which is pretty fantastic except for how walled off they are. You can't really re-use these descriptions for e.g. development, they're not vendor agnostic, and they only way to run them is by pushing your code.
Maybe it's a silly analogy but it's almost like being a web dev that doesn't have a browser and needs to send their code to a friend who can tell them if that font size looks good.
I think we're way over due for freeing these "blueprints" of our system from the confines of CI and making them portable and flexible. And containers are the technology that's enabling that.
Full disclaimer (as always): I work at Garden[0] where we're also solving that problem but taking a slightly different approach to Dagger (it's still a DAG). Garden config is declarative and the jobs (we call them actions) have a semantic meaning. You can e.g. have a Build action of type container or a Deploy action of type Helm and Garden will figure out what to do with it.
-
GitHub Actions Are a Problem
Yes, there's us over at https://github.com/garden-io/garden! We're big believers in pipelines that run anywhere. I even made a short little video that should give you the gist. [1]
Some of the short-list of differences: we use YAML for our configuration language, Dagger can use full-fat languages to define its pipelines. Our feature scope is broader: you can use us to vend IDP-like stacks to your developers if you're a Platform Team; we make development with remote Kubernetes clusters very easy, including all the remote image builds; and we have a number of integrations so you can bring your IaC tool of choice (Pulumi, Terraform) into your pipeline and set up service -> infra dependencies.
-
The Icelandic Saga Database
Me too. In fact Garden (dev tooling for the Kubernetes)[0] is a Berlin start-up with three Icelandic founders.
And if I'm not mistaken, two of us worked briefly with @halldorel (above commenter) at an earlier Icelandic start-up. It's a small world (if you're Icelandic).
-
Local development set up for microservices with Kubernetes - Skaffold
There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com
-
Best way to run k8s apps locally
Telepresence, tilt, garden.io, okteto, skaffold etc.
-
Local Development with hot reloading, what does your team do?
- https://garden.io/
- Fast file synchronization and network forwarding for remote development
-
Deciding between Telepresence vs Garden.io
I just used garden.io for a small personal project that was more about figuring out how to use garden. I started with the examples and used the Terraform GKE example.
-
Should devs manage dev environments
A few other people in the space: garden and tilt have been around for awhile. Skaffold has also been around awhile, but I think it's a step below the others. Or at least it was back when I was evaluating.
-
Mutagen – Cloud-based development using your local tools
We use Mutagen for Garden's hot reloading mechanism. (Garden is a dev tool for K8s and hot reloading enables users to sync changes directly to a prod like dev environment as opposed to doing a rebuild and re-deploy).
It's a really a fantastic piece of technology and completely transformed the whole experience (we were using good 'ol rsync before). In particular it works seamlessly across platforms.
If anyone's interested in how we use it, it's here: https://github.com/garden-io/garden/blob/master/core/src/plu...
What are some alternatives?
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
genie - A quick way into a systemd "bottle" for WSL
Scoop - A command-line installer for Windows.
Single-GPU-Passthrough
okteto - Develop your applications directly in your Kubernetes Cluster
setup-msys2 - GitHub Action to setup MSYS2
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
UTM - Virtual machines for iOS and macOS
skaffold - Easy and Repeatable Kubernetes Development
telepresence - Local development against a remote Kubernetes or OpenShift cluster
usbip-wsl2-instructions
FFmpeg - Mirror of https://git.ffmpeg.org/ffmpeg.git