https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# lima
a
This message was deleted.
f
Note that even on macOS we check if the username is a valid Linux username, and then just fall back to 
lima
if it isn't.
b
Right, need to do the same for the home directory and the user id. Which requires mounts to have different endpoints
That is, use the Cygwin $HOME and not the Windows path (
C:\Users\…
)
And use 
id -u
and 
id -g
, instead of the uid and gid strings (Windows SID)
Changed to use the same path as on the host, instead of having different endpoints
So it will use 
/c/Users/anders
, which is also known as 
C:\Users\anders
on the host
f
This is now turning "Lima for Windows" into "Lima for Cygwin"... If I have to use Unix conventions to use it, why wouldn't I just run "Lima for Linux" inside WSL2?
b
No, it would be C:\Users\anders on the Windows side but mapped into /c/Users/anders on the Linux side
The plan was to use either MinGW (Git for Windows) or MSYS2, not cygwin and the Unix runtime it provides
The main reason is that I don't want to package bash.exe or ssh.exe and I don't want to rewrite any scripts
But it would still be regular windows programs (not unix, like cygwin) even if some concepts are needed (id, cygpath)
It is still just an experiment, I will try to make it work - but I don't know if it will be a realistic and usable option
f
Ok, good. I've never been a fan of Cygwin (even though I used parts of it for a long time), because it always felt like a kludge. MSYS2 feels much more "native" (but didn't have all the pieces I needed, like 
sshd
).
b
I have never used DOS or Windows, went from the Mac straight to Unix. And then ended up on Linux, in the end.
At one point I was using "Office" as my main OS, and there it turned out Windows was the most compatible one 🙂
f
I had to build software for AIX, HP-UX, Linux, OS X, Solaris, and Windows, so scripting the "build system" was challenging
b
Indeed. It was /bin/sh and workarounds
Too much m4 that you can never unlearn
f
That I fortunately avoided completely... Perl for everything and forever! :P
😀 1
b
I kinda miss Perl and Ruby, too much python or python3 or python3.10 these days <sigh>
f
So it looks like I'm still the official maintainer of 
README.win32
for Perl5 (and one of the authors of 
README.cygwin
) 🙂
Although I've retired from actively maintaining Perl for over 10 years now
b
Congratulations! I never knew that I would be running virtual machines on Mac and Win, when I signed up to work with containers on Linux
Maybe next year ? (The Linux desktop)
f
The Mandalorian says: It is the way!
I think WSL2 is pretty much where Linux on the Desktop is going
b
Yeah, VM forever
f
Pulse Audio on Windows, what a time to be alive! 😂
b
People even want a VM on Linux, just to feel “at home”. Not so much for isolation, just to make it like Mac or Win
f
What?
I do understand wanting a VM for containers, so you can quickly wipe and reinstall though
b
f
Yeah, we had no plans to do Rancher Desktop for Linux, but there were a significant number of people asking for it, so we added it as well
Actually I think we had it before Docker 🙂
b
Benefit of the web app, I think Podman was reconsidering their Mac-only app as well
Making me sad, think I will work with something else - back to the Raspberry Pi perhaps.
f
Do you just do this for fun, or do you also need it for work?
b
It was work (for learning Docker and Kubernetes development), now it is more of a hobby
f
For personal use, I never needed kubernetes; just plain docker or docker-compose is always enough for me
b
Otherwise it is normally embedded Linux or Android, or cloud systems (so either “smaller” or “bigger” than desk)
We had three form-factors: docker-machine, minikube, small 4-node cluster - and then on to production (the shared cloud nodes, that is)
f
I'm happy to be working on desktop software again. I worked on Cloudfoundry (for Kubernetes) for many years, and it was so tedious, making changes, waiting 30min-2h for CI to do a full cycle...
By the time CI was done, I had already forgotten why I made the change in the first place 😄
Anyways, good luck with the Lima for Windows port! I'm curious how it turns out, even though I think WSL2 will continue to have the edge in the end
b
You are probably right. I might include it in the minikube QEMU driver, but I’m not sure it will be more than an open and portable alternative
5 Views
Open in Slack
PreviousNext
Powered by