I can. You can't. That is the difference. (besides your mssql, but why the heck would I run a thousand $ software in a docker)
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Docker Desktop for Mac Updated With Apple Silicon Support
- Thread starter MacRumors
- Start date
- Sort by reaction score
Again, you seem to think your way is the only way. It's not.
BTW, Sql Server Developer is free.
And you can what exactly?
There's plenty of creativity in software development: by nature, it's creative. It's very difficult to solve a problem if you don't understand the problem. If you think programming is boring, then it's probably not for you. There's many, whoever, who think software development is an interesting career choice. Of course, the business domain is of course, important for interest.
If a gadget helps with teaching kids to code, that's all good. Gadgets are nothing new, it's been like that for decades. In the 80s, there was the turtle robot that you could move around via programming, for instance.
Last edited:
le me simplify thing. As i mention before not just pure joke sybase. Sybase and sql server before same code which sybase can be both world linux and windows while sql server on windows only.Interesting points.
Can you tell me, how it was done in pre-docker-times? I can only learn...
Why i do thing sql server much better then MySQL ,store procedure. You type and test on fly while MySQL you need to compile to test it.
Why does docker help sql server in macos ?
By native is easier to microsoft and us to maintain the database. In old ways, most best basic is 3 server (email, host server,database) which nowdays you can spin saparate vm, docker or whatever new term you can call it.
** most people don't think c# and sql server couldn't run in macos . Yes you can.
** this is not for warflame database but focus how m1 can do the same thing as intel counterpart.@TiggrToo.
The annoying part is that it shouldn't be a problem in theory, but those things are so non-portable. Even Postgres was annoying until they made Postgres.app, which is great.
I should have been more clear about my use case.
I'm a software developer so sharing RAM with Docker means hobbling or disabling the IDE experience on 16 gb Macs. I recommend 32 gb-- 16 gb set aside for Docker and 16 gb for everything else your OS uses. Applications like SQL Server in Linux can be very demanding in terms of both memory and disk usage so the more RAM, the better.
It all depends on your use case. If you're making small images and containers with few dependencies and low overhead then a 16 gb system can work fine for Docker.
On behalf of the entire development community, and MacRumors, I would like to thank you for your valuable contribution.
And Red Hat is IBM since 2019.
Edit: oh geez, it looks like every company has to have at least one Hype Driven Developer.
Last edited:
There is a downside when they're afraid that everyone learning to code = losing their job or lower compensation from their employer. Which is why always improving your knowledge, skills, and abilities with growing technologies, like Docker, is important.
for my work load normally 10 GB in 16 GB ram. If i do some work in docker which mean i need more ram while my imac 2017 max 16 GB and my macbook m1 just 8 GB . I prefer/required separate pc which can bought as dumb server cost around 300 dollar to 500 instead rely on mac.
That's either you didn't live in software development.
Code Monkey - doesn't care about business process, they just do as they said so. They don't solve problem.
System Analyst/System Architect - deal with base code / infra (maybe docker/kubernates or what ever)
You miss understanding the concept. It's never about CODE, FRAMEWORK. It's about delivery to solve problem. Talk with codemonkey then you deal all those code /framework.
+1 I have 8 gb m1 too. With Apple memory prices, it's just cheaper to spin up an aws spot instance when needed to be used as docker engine.
Can someone tell me what Docker is?
I understand it lets you run software on any system, but does this mean its an emulator? Can it be used for stuff like Microsoft Office? Do you download a Docker app and launch the software from there or do you download the software already wrapped with docker, just download and launch?
I understand it lets you run software on any system, but does this mean its an emulator? Can it be used for stuff like Microsoft Office? Do you download a Docker app and launch the software from there or do you download the software already wrapped with docker, just download and launch?
No, it’s not an emulator. It uses the kernel of the host OS. In the case of MacOS, it leverages Apple’s Hypervisor technology (with a tool called hyperkit) to create a Linux VM to run Linux containers. Here’s a good document about how it works:
What is Docker? - .NET
.NET Microservices Architecture for Containerized .NET Applications | What is Docker?
docs.microsoft.com
Hypervisor | Apple Developer Documentation
Build virtualization solutions on top of a lightweight hypervisor, without third-party kernel extensions.
Its most common use is to emulate a server environment on your local machine for development purposes. The nice thing is that once you create that environment, you can actually deploy the exact environment to servers that support Docker.
Last edited:
Actually Docker also does include an x86-64 emulator for Apple Silicon (it uses the QEmu emulator). This allows cross-platform use on the M1. I’ve tested it and it is several times slower than native but depending on what you need it might be adequate.No, it’s not an emulator. It uses the kernel of the host OS. In the case of MacOS, it leverages Apple’s Hypervisor technology (with a tool called hyperkit) to create a Linux VM to run Linux containers. Here’s a good document about how it works:
What is Docker? - .NET
.NET Microservices Architecture for Containerized .NET Applications | What is Docker?docs.microsoft.com
Hypervisor | Apple Developer Documentation
Build virtualization solutions on top of a lightweight hypervisor, without third-party kernel extensions.developer.apple.com
Its most common use is to emulate a server environment on your local machine for development purposes. The nice thing is that once you create that environment, you can actually deploy the exact environment to servers that support Docker.
I've used it when no alternative exists and it does work pretty well. I ran a full x86 ubuntu really well. No question ARM images work way better.
I use it to spin up my services I'm developing before deploy.
Guess then the best way to describe it without breaking barriers of abstraction is that it runs Linux containers. VMs, emulators, etc may lie beneath depending on the platform.
Or am I wrong about that too, and it can run other kinds of containers?
For me, my thinking those things as all in one apps no need thinking how to set up those nasty configuration. But for normal user like me, we don't have multiple network port so practically if wanted to implement own virtual network only.
That seems accurate though I don't know what it does on Windows. I guess it uses WSL which still seems to fit your description.
It can also run Windows docker containers, but only on Windows.
Docker: Accelerated Container Application Development
Docker is a platform designed to help developers build, share, and run container applications. We handle the tedious setup, so you can focus on the code.
www.docker.com
... I'm just gonna give up and call it a VM even though that's inaccurate.It can also run Windows docker containers, but only on Windows.
Docker: Accelerated Container Application Development
Docker is a platform designed to help developers build, share, and run container applications. We handle the tedious setup, so you can focus on the code.
Here's my attempt at a layman answer:
'Regular people' probably would never use a Docker container directly, but for now, just know that many of the services and applications you use, may use containers as part of their product or service, or developers used containers to build those services.
In layman terms, a Docker container is comparable to a VM, but containers are lighter, quicker to deploy, but more dependent on your operating system. These are trade offs the developer considers when deciding on whether to run a full VM vs running a container as part of their development process. And this is not a 'use one or the other' situation. You can use containers and VMs together.
Container can't (easily) run apps from other operating systems. That is the advantage of a VM: you want to run a Windows app on your Mac? Download a hypervisor (such as VMWare, Virtual Box, Parallels), download Windows, create a VM and run your app. A disadvantage is that you are downloading an additional full OS, and creating VMs (which each contain the OS) can take up much more space than using containers, which share/reuse resources between themselves.
As said before, containers, unlike VMs, are very dependent on your host OS to help run applications/processes. The advantage is that everything has a much smaller footprint on your computer as you're using the host OS vice downloading another OS, to run the application. The disadvantage is that since Docker needs direct help from your host OS to run the app in your container, the container needs to be the same OS as the host. So no (simple way) of running that Windows app you want to use in a container on a Mac, as a Windows container would not get the help it needs from macOS.
So a common scenario is a developer, working in Linux, creating a solution that may go to a different flavor of Linux. As all flavors of Linux share the same OS kernel, this is no problem. The container will receive the help from the kernel it needs.
And this leads back to your original question: No, an average user has no direct use for Docker, but it is a valuable tool for developers.
It doesn't need the same OS as the host. For Windows, that's a special case as it's... Windows. But the containers use Linux as a base. The idea is a container will run enough to get something up and share resources on the Host. You can scale many more containers vs VMs. Plus they are isolated and easy to provision and tear down.