131–140 of 284 posts
Simple: I never target specific CPUs to begin with ;) I'm only half joking. I'm of the group of people who know that Docker is a security nightmare unless you're generating your Docker images yourself, so wherever I've had to support that, I insist on that. If you don't use software that's either processor centric (and therefore buggy, IMHO) or binary-only, then this is straightforward and a win for everyone. Run x86…
I got an M1 MacBook Pro from work last year, and expecting to pay the price for being an early adopter, I set up my previous Intel-based MBP nearby in case I ran into any problems or needed to run one of my existing virtual machines. (I do varied development projects ranging from compiling kernels to building web frontends.) In reality I have hardly turned on the Intel MBP at all since I got it. At all. Docker and VM…
..want to get rid of your old intel MBP? The video on my 2017 is dying.
Earlier quoted context omitted.
Alternative theory: Apple doesn't offer an M1 server. Github doesn't offer an M1 build server because M1 servers don't exist.
Apple also doesn’t offer an x86 “server” yet Azure DevOps offers Mac build servers.
The rest of us is still running on racks of Mac Minis
Our entire dev team switched from MacBooks to laptops running linux.
The main pain point with running linux on a laptop is finding a suitable pairing of the hardware and software so that everything works (device driver support, no bios/uefi/acpi bugs, etc).
Finding some good hardware to run linux only has to be done once maybe every 3-4 years and them you can just carbon copy the setup for all of your devs.
Heck, I will save you some work: the dell XPS 13 works great with the latest stable release of Ubuntu.
I work at a SaaS vendor. We are completing a project to upgrade to Java 11 for most of our micro services. This will also mean we do multiarch container builds for our entire pipeline. Once that is complete, we will begin developing against ARM as the primary target for devs. This is needed because we are in the middle of a hardware refresh so by EOY, something like 80% of devs will be running on M1 Pro. This should…
I think we're entering a long period of multiarch for the "traditional" server/desktop. I expect a lot of good to come out of this on the compiling side (easier to target any OS-arch), and (perhaps more importantly) on the general cross-platform front.
Earlier quoted context omitted.
Apple also doesn’t offer an x86 “server” yet Azure DevOps offers Mac build servers.
Yes because Microsoft got a special license from Apple that allows for the virtualization of Mac OS on non Apple hardware... The rest of us is still running on racks of Mac Minis
Earlier quoted context omitted.
> It is interesting how much impact GitHub has had by not having Apple Silicon support Putting on my tin-foil hat for a sec: GitHub is owned by Microsoft, who would really stand to benefit from slowing down Apple Silicon adoption a bit...
Alternative theory: Apple doesn't offer an M1 server. Github doesn't offer an M1 build server because M1 servers don't exist.
I got an M1 MacBook Pro from work last year, and expecting to pay the price for being an early adopter, I set up my previous Intel-based MBP nearby in case I ran into any problems or needed to run one of my existing virtual machines. (I do varied development projects ranging from compiling kernels to building web frontends.) In reality I have hardly turned on the Intel MBP at all since I got it. At all. Docker and VM…
Are there more details on "docker buildx build" that you can point us to? The command line reference doesn't seem especially helpful: https://docs.docker.com/engine/reference/commandline/buildx_... E.g. if I wanted to start building ARM binaries on a x86 host, is that the sort of thing this would enable?
I found this article with some overview and example command lines: https://www.docker.com/blog/multi-arch-images/ . As best I can tell, you don't actually need a custom builder. You can just skip the `docker buildx create` and go straight to `docker buildx build` after one workaround below.
I needed the workaround from this comment to make it work (to install qemu? not sure): https://github.com/docker/buildx/issues/495#issuecomment-754...
Overall a very slick experience for going from zero to multiarch containers. Well done, Docker.
Losing eGPU really hurts. I had three-up before, and now I’m back to the laptop and one central display. I could get a cheap DisplayLink hub but the performance is poor and I’m not happy with granting their driver screen recording permission. Or trusting it at all tbh.