Yes! This what I usually do. I will develop on the host using tools installed via Homebrew, then package/build/test via docker.
And to be clear, I really love the ideas behind Bluefin and use it every day. I’ve just kind of given up on devcontainers, specifically.
Honestly, even with VSCode, devcontainers are kind of just ok, at best.
They are very fiddly. The containers keep running when you close VSCode (which makes sense, and sure the resource usage is minimal, but it’s damned annoying) and you have to stop them manually. Meanwhile the commands in VSCode to work with/activate the containers are not super clear in terms of what they actually do.
Oh, what’s that? Need a shell inside the container you’re working in for testing things out, installing dependencies, etc.? Well, I hope you pick the right one of VSCode’s crappy built in terminals! Because if you want to use a real terminal, you are stuck with the crappy devcontainer CLI to exec into the container. A CLI that is NOT up to date with, or even includes, all the commands for devcontainers in the editor (which is what makes working with them in other IDE/editors such a pain in the butt…).
And this gets me…. What? A container I can share with other developers, sure, but it’s very likely NOT the container we are actually going to deploy in. So…
Yeah, I’ve also had a lot of frustrations with devcontainers in Bluefin. I really like what the Bluefin project is doing. The reasoning behind it makes a lot of sense to me. But devcontainers are kind of pushed as the way you “should” be writing code on Bluefin and it’s…. not great.
They do have Homebrew and Distrobox though, which helps a lot. I have ended up doing most of my development work on Bluefin on the host system with tools installed via brew, which is kept separate enough from the rest of the file system to still keep things tidy.
Overall, I think Bluefin is great and it, or something like it, may very well be the future of Linux… but the future isn’t here just yet and there are some growing pains, for sure.
This looks pretty cool!
And is only ONE of the reasons Yar’s Revenge is awesome!
It’s… fine. Last job was an AWS shop, so I definitely had to learn the differences but all the commonly used stuff is in Azure too.
I can’t really make any legit complaints that don’t exist in AWS in a slightly different flavor.
Thanks for posting this. I’ve been thinking about picking it up.
I’m the “makes commits to Azure DevOps because that’s what his company uses” user, so mine looks a lot like number 4.
Yep, my birthday is very early in April. Having two Easters in the same year of my life happens from time to time.
I’ll take my Motorola Razr back from the early 00s.
Whether I do Captain Kirk impressions with it in the privacy of my own home is my business…
I guess it gives away my age, but I understand this. No idea what the other one says though.
I second this one. LEGO is really well made, the sets are well designed, and the instructions are some of the best you’ll ever see in any build-it-yourself product of any kind.
Well, the bar was low…
Ah, I see you too have run code in Azure Functions…
I agree, but knowing it’s from Norway makes me feel more comfortable with the idea of using it than if it was made in the US…. (And I’m American…)
Yes, and I like it.
But I’m really more of a Chai tea man.
I’ll be honest. After Starfield, I’m not entirely sure I want them to do it…
I the context of Linux and self-hosting “prepping” is usually more about maintaining services you find useful in a way that you can do it yourself, as opposed to relying on Google or Amazon (etc) who could pull the rug out from under you at basically any time.
That’s awesome. Very 1960s Star Trek, in a good way.