…ja, wo laufen se denn??
NUR mit einem „elevated“ Terminal (sei der Administrator, trau‘ Dich 🙂 ) sind die vm’s zu bändigen und mit docker-machine per ssh erreichbar:
Monat: Juni 2017
Docker for Windows
C:\Users\xxx\Entwicklung\Docker λ docker run -p 4000:80 friendlyhello * Running on http://0.0.0.0:80/ (Press CTRL+C to quit) C:\Users\xxx\Entwicklung\Docker λ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ee21b1b202ab friendlyhello "python app.py" 17 seconds ago Up 15 seconds 0.0.0.0:4000->80/tcp upbeat_booth C:\Users\xxx\Entwicklung\Docker λ docker run -d -p 4000:80 friendlyhello 741d25dc2f66ea2be8d89cf85001e90780b4f70a6d3c2c589796df7783c70849 docker: Error response from daemon: driver failed programming external connectivity on endpoint silly_swartz (eb2731697f9a185975656648c21ae978a4ece3ea2a7fab200a4586c2c0dca2f6): Bind for 0.0.0.0:4000 failed: port is already allocated. C:\Users\xxx\Entwicklung\Docker λ docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS C:\Users\xxx\Entwicklung\Docker λ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ee21b1b202ab friendlyhello "python app.py" 54 seconds ago Up 53 seconds 0.0.0.0:4000->80/tcp upbeat_booth C:\Users\xxx\Entwicklung\Docker λ docker stop ee21b1b202ab ee21b1b202ab C:\Users\xxx\Entwicklung\Docker λ docker run -d -p 4000:80 friendlyhello 3f5a728eaa306c01f6ab40567bd1636733aaa1b7ca01e976ff809dec58f6dc5b C:\Users\xxx\Entwicklung\Docker λ