Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VIC Container Fails with "Parsing network alias" when Using --link option (52120)

Last Updated: 3/3/2018Categories: TroubleshootingTotal Views: 2938Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Attempting to link a container to already existing container fails with message "Error response from daemon: Server error from portlayer: Parsing network alias".

Example of reproduction below.

# docker -H VCH_IP:2376 --tls run -itd --name WebProxy -p 1111:80 nginx
ae533aed2ff4ba2aaa77f71ebd28035275332d26c6e22b1153422f100b023116
# docker  -H VCH_IP:2376 --tls run -itd --name jumpshell --link WebProxy busybox
ffd7273d094bb038104933f0a749bd14859a8a185dea11315c0ccff260d21b27
docker: Error response from daemon: Server error from portlayer: Parsing network alias WebProxy failed.

Cause

The method of using "--link destination_container" is a deprecated docker behavior.

Resolution

In VIC "--link container_name" linking is already configured by default for containers on the same bridge network to connect to each other. Use "docker network ls" and "docker network inspect <network_name>" to see the networks and which containers are attached to the network. Try removing the "--link" option entirely from the create/run command for the container. This will connect to the container services.

Note: docker container hosts have the same behavior for additional docker networks created on the bridge. The out of the box configuration does not auto map on the default bridge network. For this reason, docker will not allow connection by default as --net is not specified to a user created docker network.

Example usage for the  "--link"option usage:

The mapping of an alias to a container is similar looking in that this command also starts with "--link" and supported by VIC. The difference between container linking and alias mapping is where the error is found. This is useful for situations when the container name is different than what the application requires. If the container is "WebProxy", but the application is hardcoded to connect to the name "NickName" then "--link WebProxy:NickName" can be used to make a connection to specific only to the container configured with the link. All other containers would not map NickName. This allows multiple container applications requiring to connect to the name "NickName" to map to a different service per container with a single VCH and bridge network configuration.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Integrated Containers

VMware vSphere

Related Versions:

VMware vSphere Integrated Containers 1.x

Take Our Survey

Support Assistant