User Guide

  • 04/24/2019
  • Public Content

Configure Docker* (Linux host)

Now that you’ve installed Docker, you need to configure a few Docker settings and restart the Intel® System Studio. At a high level, you need to:
  1. Enable non-root access to the Docker client commands for your user account .
  2. If you’re located behind a proxy server
    : Configure Docker and Intel System Studio proxy settings.
  3. Restart the Intel System Studio.

Enable Docker for a normal (non-root) user

By default, Docker requires root (aka sudo) privileges, but most people run Intel System Studio as a normal user. You
add the user that will be running Intel System Studio to the "docker" group. Follow the link below to:
: You can also follow these alternate instructions from the DigitalOcean site.

Configure the Docker proxy 

If you are located behind a proxy server, you may need to configure the Docker proxy settings directly, because Docker may not automatically inherit your system proxy settings. Consult your network admin to determine the correct proxy settings for your work environment, then follow the steps in the link below:
The Docker proxy instruction link above implies that you must create one
file in the
folder for each environment variable you define. This is not the case. You can create a single
file that includes multiple “Environment” declarations. For example, you could create and install a single file named “
” that looks something like the following:
You can quickly confirm that Docker has a properly configured set of proxy environment variables by typing “
docker info
” at a terminal shell command prompt (e.g., a “bash shell”). Near the end of the info page, you will see the proxy variables that you set in the
file, as in the example above. If you do not see your proxy settings in that info screen, you may need to restart the Docker daemon or restart your system.
A Docker daemon that has its proxy variables configured according to the example above will show output like the following when executing a "
docker info
" command:
... Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Http Proxy: Https Proxy: No Proxy: localhost,,::1 Registry: Experimental: false Insecure Registries: Live Restore Enabled: false ...
: You can also use "systemctl edit docker" to create overrides for Docker daemon startup options. For more information on how to do this, see
Using systemd to control the Docker daemon
. Use the "sudo systemctl cat docker" command to see how the current set of Docker startup options are configured.

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 after 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