<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Can not ping Docker Container (in VMWARE WORKSTATION 16 PRO) from HOST (UBUNTU 18.04) in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Can-not-ping-Docker-Container-in-VMWARE-WORKSTATION-16-PRO-from/m-p/2912331#M176036</link>
    <description>&lt;P&gt;I am a noob with regards to Docker/containers. My exposure has been a few hours of course videos and labs on Google Cloud with GKE.&lt;/P&gt;&lt;P&gt;From what I understand conceptually the whole point of k8s/dockers, is the convenience of not having to manage the containers (and by extension their IP addresses). Pinging the containers in essence is like managing the containers. The external environment that makes use of the containers should not try to be bound to a particular IP as there is no guarantee it will always be the same (pods can be shut down and brought up by the control plane).&lt;/P&gt;&lt;P&gt;Assuming I am wrong with the paragraph above; and that there is a use-case for pinging/managing the containers; should not this be more of a docker issue rather a Workstation Pro issue? On GKE, one would use the kubectl command so presumably with Docker you would use the docker command.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Jun 2022 11:47:44 GMT</pubDate>
    <dc:creator>bluefirestorm</dc:creator>
    <dc:date>2022-06-02T11:47:44Z</dc:date>
    <item>
      <title>Can not ping Docker Container (in VMWARE WORKSTATION 16 PRO) from HOST (UBUNTU 18.04)</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Can-not-ping-Docker-Container-in-VMWARE-WORKSTATION-16-PRO-from/m-p/2912281#M176034</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="4"&gt;Hello Community Member &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="arial,helvetica,sans-serif" size="4"&gt;I Can not ping Docker Container (in VMWARE WORKSTATION 16 PRO) from HOST (UBUNTU 18.04). both in same machine. &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="4"&gt;from the HOST IP ROUTE ADD is already done and i can ping the subnet and the route. But the containers i am not able to ping. &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&amp;gt; &lt;/FONT&gt;&lt;FONT face="LM Mono Light 10"&gt;&lt;FONT color="#FF0000"&gt;&lt;FONT size="2"&gt;&lt;SPAN&gt;sudo ip route add 192.168.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;FONT size="2"&gt;&lt;SPAN&gt;70&lt;/SPAN&gt;&lt;/FONT&gt;&lt;FONT size="2"&gt;&lt;SPAN&gt;.0/24 via 172.20.1.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;FONT size="2"&gt;&lt;SPAN&gt;47&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT color="#000000"&gt;&lt;FONT size="2"&gt;&lt;SPAN&gt;&lt;FONT color="#FF0000"&gt;dev enp0s31f6&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="4" color="#000000"&gt;In VM also i have done &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;FONT face="LM Mono Light 10"&gt;&amp;gt; sudo sysctl net.ipv4.conf.all.forwarding=1&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;FONT face="LM Mono Light 10"&gt;&amp;gt; sudo iptables -P FORWARD ACCEPT&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="4" color="#000000"&gt;I am able to ping the bridge 192.168.70.129 (interface between HOST and VM) but not able to ping the conatiners inside the VM&amp;nbsp; (192.168.7.132).&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;FONT size="4"&gt;Any advises please &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;FONT size="4"&gt;Thanks &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2022 08:18:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Can-not-ping-Docker-Container-in-VMWARE-WORKSTATION-16-PRO-from/m-p/2912281#M176034</guid>
      <dc:creator>holzhey</dc:creator>
      <dc:date>2022-06-02T08:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: Can not ping Docker Container (in VMWARE WORKSTATION 16 PRO) from HOST (UBUNTU 18.04)</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Can-not-ping-Docker-Container-in-VMWARE-WORKSTATION-16-PRO-from/m-p/2912331#M176036</link>
      <description>&lt;P&gt;I am a noob with regards to Docker/containers. My exposure has been a few hours of course videos and labs on Google Cloud with GKE.&lt;/P&gt;&lt;P&gt;From what I understand conceptually the whole point of k8s/dockers, is the convenience of not having to manage the containers (and by extension their IP addresses). Pinging the containers in essence is like managing the containers. The external environment that makes use of the containers should not try to be bound to a particular IP as there is no guarantee it will always be the same (pods can be shut down and brought up by the control plane).&lt;/P&gt;&lt;P&gt;Assuming I am wrong with the paragraph above; and that there is a use-case for pinging/managing the containers; should not this be more of a docker issue rather a Workstation Pro issue? On GKE, one would use the kubectl command so presumably with Docker you would use the docker command.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2022 11:47:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Can-not-ping-Docker-Container-in-VMWARE-WORKSTATION-16-PRO-from/m-p/2912331#M176036</guid>
      <dc:creator>bluefirestorm</dc:creator>
      <dc:date>2022-06-02T11:47:44Z</dc:date>
    </item>
  </channel>
</rss>

