Body: <p>My application need to reach a UNC path (like <code>\\server_name\folder_name</code>) from docker container.</p>
  <p>The UNC is reachable within a VPN. My app can reach it from my computer while run directly but fails to reach it while running from docker container (all the time I am connected to the VPN). I am using windows docker container.</p>
  <p>I have tried configuring it while using <code>docker network create -d transparent my-transparent-network</code> and run it using <code>docker run --network my-transparent-network --rm use_network_image</code>, but still have no network / ip address / access from container to the server. How to configure the docker to reach such UNC resource?</p>
  
Comments: CC BY-SA 4.0
Comments: 2024-10-17T08:41:10.723Z
Comments: Can you verify that the server itself is reachable from within the Docker container?
Comments: hakim00
Comments: CC BY-SA 4.0
Comments: 2024-10-20T08:26:41.510Z
Comments: It is not reachable within the Docker container, that is the problem, I can't reach no network from within the docker container
Comments: ittay
Tags: <docker><windows>
Title: How to Access UNC Path Over VPN from Windows Docker Container
UserDisplayName: ittay
ThreadText: # How to Access UNC Path Over VPN from Windows Docker Container
  
  (Asked by: username_0 on 2024-10-14)
  
  My application need to reach a UNC path (like `\\server_name\folder_name`) from docker container.
  
  The UNC is reachable within a VPN. My app can reach it from my computer while run directly but fails to reach it while running from docker container (all the time I am connected to the VPN). I am using windows docker container.
  
  I have tried configuring it while using `docker network create -d transparent my-transparent-network` and run it using `docker run --network my-transparent-network --rm use_network_image`, but still have no network / ip address / access from container to the server. How to configure the docker to reach such UNC resource?
  
  **Tags:** docker, windows
  
  > **Comments:**
  > **username_1**: Can you verify that the server itself is reachable from within the Docker container?  
  > **username_0**: It is not reachable within the Docker container, that is the problem, I can't reach no network from within the docker container  
  
  ---
  
  ## 0 answers
  
  