docker-networking

I'm trying to connect to my SQL Server instance running in my local computer using host.docker.internal (as recommended in https://docs.docker.com/docker-for-windows/networking/#use-cases-and-workarounds ) The host.docker.internal is successfully resolved to an IP, and it's ping-able And I've opened up the port 1433 in my firewall configuration Error message Connection refused 192.168.65.2:1433 My connection string Data Source=host.docker.internal,1433;Initial Catalog=;Persist Security Info=False;User ID=;Password=;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False

I'm trying to work out how to properly use swarm mode in Docker. First I tried running containers on my 2 workers and manager machine without specifying a custom network (so I'm using the default ingress overlay network). However, If I use the ingress network, for some reason I cannot resolve tasks.myservice . So I tried configuring a custom network like this: docker network create -d overlay elasticnet So now, when I bash into one of the containers, I can successfully resolve tasks.myservice but I can no longer access the port I've defined in my service creation under --publish externally

We're dockerizing our micro services app, and I ran into some discovery issues. The app is configured as follows: When the a service is started in 'non-local' mode, it uses Consul as its Discovery registry. When a service is started in 'local' mode, it automatically binds an address per service (For example, tcp://localhost:61001, tcp://localhost:61002 and so on. Hard coded addresses) After dockerizing the app (for local mode only, for now) each service is a container (Docker images orchestrated with docker-compose. And with docker-machine, if that matters) But one service can not interact

With 1.9, is there a way to start a container directly with two or more network interfaces? You can do it after the container is started with "docker network connect", but it means the process is already running and might miss the creation of the new one. This question is top doing a search regarding docker and multiple network interfaces. Although is not the required version in the question I leave here some info: With Docker 1.12+ it's possible to add more than one network interface to a docker container, but it is needed to create the container first and then attach the second (and

I have the following docker-compose file: version: "3" services: scraper-api: build: ./ATPScraper volumes: - ./ATPScraper:/usr/src/app ports: - "5000:80" test-app: build: ./test-app volumes: - "./test-app:/app" - "/app/node_modules" ports: - "3001:3000" environment: - NODE_ENV=development depends_on: - scraper-api Which build the following Dockerfile 's: scraper-api (a python flask application): FROM python:3.7.3-alpine WORKDIR /usr/src/app COPY requirements.txt ./ RUN pip install --no-cache-dir -r requirements.txt COPY . . CMD ["python", "./app.py"] test-app (a test react application for the