Run Macos On Docker For Windows

Estimated reading time: 6 minutes

The fastest and easiest way to get started with Docker on Windows. Docker Desktop for Mac.

Docker Desktop for Mac is the Community version of Docker for Mac.You can download Docker Desktop for Mac from Docker Hub.

By downloading Docker Desktop, you agree to the terms of the Docker Software End User License Agreement and the Docker Data Processing Agreement.

What to know before you install

README FIRST for Docker Toolbox and Docker Machine users

If you are already running Docker on your machine, first readDocker Desktop for Mac vs. Docker Toolbox to understand theimpact of this installation on your existing setup, how to set your environmentfor Docker Desktop on Mac, and how the two products can coexist.

Relationship to Docker Machine: Installing Docker Desktop on Mac does not affect machines you created with Docker Machine. You have the option to copy containers and images from your local default machine (if one exists) to the Docker Desktop HyperKit VM. Whenyou are running Docker Desktop, you do not need Docker Machine nodes running locally (or anywhere else). With Docker Desktop, you have a new, nativevirtualization system running (HyperKit) which takes the place of theVirtualBox system. To learn more, see Docker Desktop for Mac vs. Docker Toolbox.

System requirements

Your Mac must meet the following requirements to successfully install Docker Desktop:

Mac hardware must be a 2010 or a newer model, with Intel’s hardware support for memory management unit (MMU) virtualization, including Extended Page Tables (EPT) and Unrestricted Mode. You can check to see if your machine has this support by running the following command in a terminal: sysctl kern.hv_support
If your Mac supports the Hypervisor framework, the command prints kern.hv_support: 1.
macOS must be version 10.13 or newer. That is, Catalina, Mojave, or High Sierra. We recommend upgrading to the latest version of macOS. Best anti-virus and vpn for macos osx.
If you experience any issues after upgrading your macOS to version 10.15, you must install the latest version of Docker Desktop to be compatible with this version of macOS.
Note: Docker supports Docker Desktop on the most recent versions of macOS. That is, the current release of macOS and the previous two releases. Docker Desktop currently supports macOS Catalina, macOS Mojave, and macOS High Sierra.
As new major versions of macOS are made generally available, Docker stops supporting the oldest version and support the newest version of macOS (in addition to the previous two releases).
At least 4 GB of RAM.
VirtualBox prior to version 4.3.30 must not be installed as it is not compatible with Docker Desktop.

What’s included in the installer

The Docker Desktop installation includes Docker Engine, Docker CLI client, Docker Compose, Notary, Kubernetes, and Credential Helper.

Install and run Docker Desktop on Mac

Double-click Docker.dmg to open the installer, then drag the Docker icon to the Applications folder.
Double-click Docker.app in the Applications folder to start Docker. (In the example below, the Applications folder is in “grid” view mode.)
The Docker menu in the top status bar indicates that Docker Desktop is running, and accessible from a terminal.
If you’ve just installed the app, Docker Desktop launches the onboarding tutorial. The tutorial includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub.
Click the Docker menu () to seePreferences and other options.
Select About Docker to verify that you have the latest version.

Congratulations! You are now successfully running Docker Desktop.

If you would like to rerun the tutorial, go to the Docker Desktop menu and select Learn.

Uninstall Docker Desktop

To unistall Docker Desktop from your Mac:

From the Docker menu, select Troubleshoot and then select Uninstall.
Click Uninstall to confirm your selection.

Note: Uninstalling Docker Desktop will destroy Docker containers and images local to the machine and remove the files generated by the application.

Switch between Stable and Edge versions

Docker Desktop allows you to switch between Stable and Edge releases. However, you can only have one version of Docker Desktop installed at a time. Switching between Stable and Edge versions can destabilize your development environment, particularly in cases where you switch from a newer (Edge) channel to an older (Stable) channel.

For example, containers created with a newer Edge version of Docker Desktop maynot work after you switch back to Stable because they may have been createdusing Edge features that aren’t in Stable yet. Keep this in mind asyou create and work with Edge containers, perhaps in the spirit of a playgroundspace where you are prepared to troubleshoot or start over.

To safely switch between Edge and Stable versions, ensure you save images and export the containers you need, then uninstall the current version before installing another. For more information, see the section Save and Restore data below.

Save and restore data

You can use the following procedure to save and restore images and container data. For example, if you want to switch between Edge and Stable, or to reset your VM disk:

Use docker save -o images.tar image1 [image2 ..] to save any images you want to keep. See save in the Docker Engine command line reference.
Use docker export -o myContainner1.tar container1 to export containers you want to keep. See export in the Docker Engine command line reference.
Uninstall the current version of Docker Desktop and install a different version (Stable or Edge), or reset your VM disk.
Use docker load -i images.tar to reload previously saved images. See load in the Docker Engine.
Use docker import -i myContainer1.tar to create a filesystem image corresponding to the previously exported containers. See import in the Docker Engine.

For information on how to back up and restore data volumes, see Backup, restore, or migrate data volumes.

Run Macos On Docker For Windows 7

Where to go next

Getting started provides an overview of Docker Desktop on Mac, basic Docker command examples, how to get help or give feedback, and links to other topics about Docker Desktop on Mac.
Troubleshooting describes common problems, workarounds, howto run and submit diagnostics, and submit issues.
FAQs provide answers to frequently asked questions.
Release notes lists component updates, new features, andimprovements associated with Stable releases. For information about Edge releases, seeEdge release notes.
Get started with Docker provides a general Docker tutorial.

mac, install, download, run, docker, local-->

By Rick Anderson

AOL is back for Mac. AOL is reaffirming its commitment to Mac users with the first release of a brand new, all-in-one web software, now available for download: AOL Desktop for Mac. The best part. Apr 11, 2018 4 Reasons Why You'll Love AOL Desktop 9.7 for PC: 1. You're connected - Get access to your online world, all in one easy-to-use place. Stay connected with AOL Mail, chat on AIM with family and friends, and be in-the-know with world news and entertainment on AOL.com. AOL Desktop for Mac continues to provide the best all-in-one Internet experience with improved mail, Web browsing, toolbars and a new version of AIM. You will get the true AIM Experience - AIM for Mac allows you to select your own Buddy sounds, wallpaper and animated Buddy Icons. Dec 24, 2017 AOL Desktop for Mac continues to provide the best all-in-one Internet experience with improved mail, Web browsing, toolbars and a new version of AIM. You will get the true AIM Experience - AIM for Mac allows you to select your own Buddy sounds, wallpaper and animated Buddy Icons from the AIM Expressions library. Aol desktop for mac mojave mac.

Macos Docker Install

ASP.NET Core uses HTTPS by default. HTTPS relies on certificates for trust, identity, and encryption.

This document explains how to run pre-built container images with HTTPS.

See Developing ASP.NET Core Applications with Docker over HTTPS for development scenarios.

This sample requires Docker 17.06 or later of the Docker client.

Prerequisites

The .NET Core 2.2 SDK or later is required for some of the instructions in this document.

Certificates

A certificate from a certificate authority is required for production hosting for a domain. Let's Encrypt is a certificate authority that offers free certificates.

This document uses self-signed development certificates for hosting pre-built images over localhost. The instructions are similar to using production certificates.

For production certs:

The dotnet dev-certs tool is not required.
Certificates do not need to be stored in the location used in the instructions. Any location should work, although storing certs within your site directory is not recommended.

The instructions contained in the following section volume mount certificates into containers using Docker's -v command-line option. You could add certificates into container images with a COPY command in a Dockerfile, but it's not recommended. Copying certificates into an image isn't recommended for the following reasons:

It makes difficult to use the same image for testing with developer certificates.
It makes difficult to use the same image for Hosting with production certificates.
There is significant risk of certificate disclosure.

Docker Run Windows Service

Running pre-built container images with HTTPS

Use the following instructions for your operating system configuration.

Windows using Linux containers

Generate certificate and configure local machine:

In the preceding commands, replace { password here } with a password.

Run the container image with ASP.NET Core configured for HTTPS in a command shell:

When using PowerShell, replace %USERPROFILE% with $env:USERPROFILE.

The password must match the password used for the certificate.

macOS or Linux

Generate certificate and configure local machine:

dotnet dev-certs https --trust is only supported on macOS and Windows. You need to trust certs on Linux in the way that is supported by your distro. It is likely that you need to trust the certificate in your browser.

In the preceding commands, replace { password here } with a password.

Run the container image with ASP.NET Core configured for HTTPS:

The password must match the password used for the certificate.

Windows using Windows containers

Generate certificate and configure local machine:

In the preceding commands, replace { password here } with a password. When using PowerShell, replace %USERPROFILE% with $env:USERPROFILE.

Run the container image with ASP.NET Core configured for HTTPS:

The password must match the password used for the certificate. When using PowerShell, replace %USERPROFILE% with $env:USERPROFILE.