News for hackers. Stuff that matters.
Re:Docker Compose best practices for dev and prod by tmpz22 on Tuesday August 16, 2022 @02:00PM (#32486438)
You're trying to create a uniform developer experience across two platforms that are wildly different.

If you find yourself spending a ton of time on a one-size-fits-all-disappoints-everybody solution, maybe its time to build two effective solutions instead.

Re:Docker Compose best practices for dev and prod by bluedino on Tuesday August 16, 2022 @02:15PM (#32486620)
That's kind of the point if containers, isn't it?
Re:Docker Compose best practices for dev and prod by DrBenCarson on Tuesday August 16, 2022 @02:56PM (#32487175)
No definitely not. In fact to this day containers only run on Linux. Your Mac or PC just runs a Linux VM in order to be able to run any containers.

Containers are not meant to make anything OS-agnostic. Containers are just a way of running Linux

Re:Docker Compose best practices for dev and prod by jiggawatts on Tuesday August 16, 2022 @09:05PM (#32491049)
Not quite true: Windows containers run natively on Windows. As of Windows 11, even Server 2022 containers can run using process isolation.

Something hilarious to me is that "multi-arch" images are a thing, and can result in the same dockerfile building a Windows image on a Windows PC, and a Linux image on a Linux PC!

Re:Docker Compose best practices for dev and prod by sneak on Wednesday August 17, 2022 @02:00AM (#32492832)
This is a red herring and this feature only exists as a Microsoft platform strategy. I don’t know of anyone real using Windows executable docker containers on Windows hosts.

dockerd for windows isn’t even free software, last I looked.

Re:Docker Compose best practices for dev and prod by tmpz22 on Tuesday August 16, 2022 @02:20PM (#32486672)
Oh god no, Linux containers were not intended to be the solution for cross compatibility issues between Windows and MacOS