User Guide

  • 04/24/2019
  • Public Content

Configure Docker Toolbox for Windows

Now that you’ve installed Docker, you may need to configure a few Docker settings before you restart the Intel® System Studio. At a high level, you need to:
  1. Make sure Docker Toolbox is running.
  2. If you’re located behind a proxy server
    : Configure Docker and Intel System Studio proxy settings.
  3. Restart the Intel System Studio.

Make sure Docker Toolbox is running

Unlike Docker for Windows, Docker for Mac and Docker on Linux, Docker Toolbox
will not automatically start when you reboot or login to your machine
. You must start it manually before starting Intel System Studio or create an autostart script to start it automatically.

Manual configuration of Docker Toolbox proxy settings

If you have problems (the "
Docker Quickstart Terminal
" shortcut fails to complete or your PROXY env variables did not get set), perform the following steps:
The quote characters " and the UPPER-CASE characters in
of the commands below are essential to making sure you can configure Docker Toolbox. Be sure to copy and enter the commands correctly!
> cd "%ProgramFiles%\Docker Toolbox" > "%ProgramFiles%\Git\bin\bash.exe" $ export HTTP_PROXY= $ export HTTPS_PROXY= $ export NO_PROXY=localhost,,::1 $ docker-machine rm -f default $ rm -rf ~/.docker/machine/machines/default $ docker-machine create -d virtualbox --engine-env HTTP_PROXY=$HTTP_PROXY --engine-env HTTPS_PROXY=$HTTPS_PROXY --engine-env NO_PROXY=$NO_PROXY "default"
The proxy settings shown above will
work, they are for illustration. You 
 need to change the 
 lines that configure the names and ports to match your proxy server.
Consult your network admin to determine the correct proxy settings for your work environment.
After performing the previous commands that configured the Docker Toolbox proxy, open a
shell and execute the following commands:
> @FOR /f "tokens=*" %i IN ('docker-machine env default') DO @%i > docker info ... Debug Mode (server): true File Descriptors: 17 Goroutines: 26 System Time: 2017-10-14T00:31:41.981752454Z EventsListeners: 0 Http Proxy: Https Proxy: No Proxy: localhost,,::1 Registry: Labels: provider=virtualbox Experimental: false Insecure Registries: Live Restore Enabled: false   > docker version Client: Version: 17.07.0-ce API version: 1.31 Go version: go1.8.3 Git commit: 8784753 Built: Tue Aug 29 17:41:05 2017 OS/Arch: windows/amd64 Server: Version: 17.09.0-ce API version: 1.32 (minimum version 1.12) Go version: go1.8.3 Git commit: afdb6d4 Built: Tue Sep 26 22:45:38 2017 OS/Arch: linux/amd64 Experimental: false
From this point forward, you should be able to use the "Docker Quickstart Terminal" icon to start the Docker Engine (daemon) and to configure your shell environment so you can connect to the Docker Engine with commands like "
docker exec
" and "
docker ps -a
" and "
docker images
" etc.
If that does not work, you can start the Docker Engine manually using the following commands from a
> docker-machine status Stopped > docker-machine start "default" > docker-machine regenerate-certs "default" > docker-machine status Running > @FOR /f "tokens=*" %i IN ('docker-machine env default') DO @%i > docker info ...

Configure the Intel System Studio proxy

Unfortunately, Docker and Eclipse* do not share their proxy information. Therefore, if you are working behind a proxy server, you may also need to configure the Intel System Studio (Eclipse) proxy, in addition to the Docker proxy (described above). Follow the link below to:
Consult your network admin to determine the correct proxy settings for your work environment.
: In some proxy environments, setting the Eclipse SOCKS proxy may interfere with the ability of Intel System Studio to access Internet resources. In this case, the specific error messages provided by Intel System Studio may be misleading. This is a known problem with Eclipse. We recommend that you leave the SOCKS proxy setting empty in the Eclipse proxy settings panel.

Exit and restart Intel System Studio

Now that Docker is installed, running, and configured,
you must exit and restart Intel System Studio
This is because Intel System Studio configures its environment (the PATH and other environment variables) when it starts. Since Docker may have updated the system environment variables, it is necessary to restart Intel System Studio so it is aware of all such changes.
: If you make further changes to the Docker environment, or start Docker
you have started Intel System Studio, it may be necessary to exit and restart Intel System Studio before it can access these changes.

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804