Using Docker on Windows with Cisco AnyConnect VPN in non-split tunnel mode - gist:d2eabbd402741ae728ef6ab2985dfddd. Cisco ASA Anyconnect In this lab, we will look at Cisco ASA anyconnect remote connection on a site. On the left corner, there is a client that tries to connect network branch using anyconnect. Authorization will be verified by an Active Directory for the client.
| Start docker before connecting vpn (to get local ip, eg 192.168.99.100) |
| After start, connect to VPN, then follow next steps: |
| From: https://github.com/boot2docker/boot2docker/issues/628 |
| Add port forwarding to the NAT'd adapter in VirtualBox, add: |
| docker: host=127.0.0.1 port=2367 guest ip=[blank] guest port=2376 |
| container port: 127.0.0.1, port=[the container exposed port to forward] guest ip=[blank], guest port[container port] |
| From https://www.iancollington.com/docker-and-cisco-anyconnect-vpn/ |
| In Docker Quickstart Terminal, to point to port forwarded Docker, and to turn off checking of SSL certs: |
| export DOCKER_HOST=tcp://127.0.0.1:2376 |
| alias docker='docker --tlsverify=false' |
| Alternatively, create a new docker-machine with tlsverify turned off: |
| docker-machine create -d virtualbox --engine-env DOCKER_TLS=no default |
| export DOCKER_HOST=tcp://127.0.0.1:2376 |
| docker-machine regenerate-certs |
| - now you should be able to run docker commands without adding the --tlsverify=false |
commented Apr 14, 2018
Any ideas on how to do this for my scenario ? Any help is greatly appreciated. Bridge for mac os. |
commented Jan 31, 2020
commented Jan 31, 2020
Regardless of whether h/w virtualization is enabled in BIOS, you can't run Hyper-V and start a VirtualBox VM with a 64bit guest running at the same time. @mithuns search for 'windows hyper-v running VirtualBox at the same time' or similar terms and you'll find solutions. Easiest answer, use one or the other, but not both at the same time |
Cisco Anyconnect Docker Networking App
Cisco Anyconnect Updates