The Docker daemon pulled the 'hello-world' image from the Docker Hub. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.
From Shinyproxy issues:
shrektan commented on 29 AugHi, I would like to use shinyproxy on OSX.
It seems like the only way to connect to the daemon of Docker For Mac, is using unix:///var/run/docker.sock. However, if I change url to unix:///var/run/docker.sock in application.yml, an error occurs:
Status code: 500Message: Failed to start container: unknown protocol: unixAfter some digging, get the workaround that works:
socat TCP-LISTEN:2375,range=127.0.0.1/32,reuseaddr,fork UNIX-CLIENT:/var/run/docker.sockIt takes me two hours to find the workaround. I guess other people who using OSX will need it as well. Please add it to the documentation if you're in convenient.
Thanks.@tverbekeOwnertverbeke commented on 29 AugMany thanks @shrektan for sharing! We will add this to the docs. To be sure I understand:
you leave url: http://localhost:2375 inside the application.yml fileyou execute$ socat TCP-LISTEN:2375,range=127.0.0.1/32,reuseaddr,fork UNIX-CLIENT:/var/run/docker.sockas a plain useryou launch shinyproxy using java -jar shinyproxy-0.9.4.jarand it works?@shrektan
shrektan commented on 30 Aug@tverbeke yes, it works. Of course, I need to execute brew install socat in the terminal first (if anyone doesn't have brew on his/her OSX, go to https://brew.sh/).
The Docker Engine is a highly configurable software product, and can sometimes be complicated. These tips are put together to help users setup docker to work inside a networked proxy.
Docker Toolbox is now the legacy offering from Docker for platforms that are not supported by Docker for Windows and Docker for Mac.
Docker Toolbox is the most common method for installing docker on Mac and Windows systems. You can find instructions for download and install on the docker website. When using the docker engine under toolbox, Docker will install a small virtual machine (boot2docker) using VirtualBox, that is used to run the Docker Host Engine.
Configure your proxies manually
You can use a proxy close to use, for example:
yourproxy.net:8080
.- Open a command prompt and connect to the default virtual machine using
docker-machine
. - Edit the /var/lib/boot2docker/profile file to add the registry, become root with
sudo -i
command. - Restart the docker service:
Configure proxies with docker-machine
On windows host running docker toolbox, it's possible to use docker-machine to automatically configure your boot2docker image with proper proxy settings. Here are some quick steps on how to use docker-machine to perform this action.
- Open a cygwin shell prompt or equivalent bash shell prompt on your windows system. If you do not have one yet, you can also use the GitHub Enterprise Desktop to get a mintty shell prompt with these capabilities from here: https://desktop.github.com/ Run these commands in your prompt:
- In the same shell prompt, you can now remove the pre-existing default machine that was setup in VirtualBox. Note, this will delete all containers from your virtual machine.
- Recreate the default machine, but this time we can specify all the proxy options:Optionally include these options to adjust the Virtual machine resources.
- Edit
/etc/default/docker
- Restart docker:
sudo service docker restart
Run the following commands:
Docker for Windows is the current offering from Docker to run Docker on Windows. Docker for Windows requires Windows 10 Professional or Enterprise and Hyper-V.
Docker for Windows creates a Hyper-V VM that runs MobyLinux. Your Docker containers run in the Hyper-V VM.
Installation
Before installation, ensure Hyper-V is enabled in your BIOS and you have enabled Hyper-V in Windows Features.
At the end of installation, Docker may ask to make changes to your BIOS - say no. There are some conflicts with Bitlocker and your TPM/BIOS may get corrupted - possibly requiring a re-image. Manually make the Hyper-V changes mentioned above.
You can find Docker for Windows Installation here. This provides best experience on Windows for running Linux based containers.
Proxy Settings
Complete these steps before you attempt to use Docker. If you have not configured the web proxies Docker will be able to download container images.
When is reported Docker as running, you can right click the whale in notifications and select Settings. Choose Proxies, select Use proxy server and enter the URLs for the 'local' proxy servers. The following examples show the proxy servers.
These will then be passed down to Docker and any containers started.Note: skipping the http(s) prefixes, can cause problems for Ubuntu apt-get.
Enter yourdomain.net in the 'Bypass proxy settings for these Hosts & Domains' text field.
Click on the Apply button, Docker (the Hyper-V VM) will restart. This will take some time on the standard issue laptops. Wait for Docker to restart.
If you navigate away for the Networking 'tab', your changes will be discarded.
Select the 'Docker Daemon' settings tab. Enter the URL for your registry hub ('yourregistry.net') in the 'registry-mirrors' field. The text field will run syntax-checks on your changes. The field should now read thus.
Apply your changes by clicking the Apply button. Docker will restart.
You can control the share of memory and CPU assigned to Docker on the Advanced 'tab' of the Docker Settings tool.
McAfee Firewall Issues
When sharing a PC drive with Docker (Settings / Shared Drives), you may get a firewall error message (McAfee log - Block NetBIOS TCP incoming). Since we cannot easily affect the McAfee rules, here is a workaround...
Go to Settings / Network and set the Subnet Address to the same as your PC (it is probably the default 10.0.75.0). Example: PC IP is 1.2.3.4, set to 1.2.3.0. Press apply and when Docker has restarted you should be able to share a PC drive with Docker.Note: this solution will cause Docker to be assigned the IP x.x.x.1 which could cause IP conflicts. It is not clear how visible this IP is outside of your machine. Any other suggestions would be appreciated.
See this article on MSDN to install native Docker on Windows server.
Below are instructions to make it work your proxy network.
Setup proxy settings
Install Docker
- Enable containers feature with command:
- Restart computer
- Install docker from nuget packages
- Install Base Container
Run a Native windows container
Reference
- You can now run Windows Native containers on Windows 10 (development only)
- Example windows containers
- Azure templates https://github.com/Azure/azure-quickstart-templates
You can find Docker for Mac installation here. This provides best experience on Mac OS for running Linux based containers.
Contributions welcome