驱动程序外部连接失败

Question

有时，当我启动Jhipster注册中心时，我会得到这个错误。

 C:\DEV\GITLAB\docker.compose>docker-compose -f jhipster-registry.yml up
    Starting dockercompose_jhipster-registry_1 ... error

ERROR: for dockercompose_jhipster-registry_1  Cannot start service jhipster-registry: b'driver failed programming external connectivity on endpoint dockercompose_jhipster-registry_1 (4d7fb5c0e58ffbe825abc1d6ec7fa07ff19d61916647b8b74e82cf90437da7aa): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8761:tcp:172.19.0.2:8761: input/output error'

ERROR: for jhipster-registry  Cannot start service jhipster-registry: b'driver failed programming external connectivity on endpoint dockercompose_jhipster-registry_1 (4d7fb5c0e58ffbe825abc1d6ec7fa07ff19d61916647b8b74e82cf90437da7aa): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8761:tcp:172.19.0.2:8761: input/output error'
ERROR: Encountered errors while bringing up the project.

看起来它不会启动，因为端口被占用了。所以我用多个程序来看这个

尝试：

_Netstat / Resource / TCPvie_w，但他们中没有人能看到任何东西占用该端口。

docker-compose down

它是通过重新启动窗口来临时修复的。它也是由重新启动码头固定。

jhipster注册公司：

 version: '2'
services:
    jhipster-registry:
        image: jhipster/jhipster-registry:v3.2.4
        volumes:
            - ./central-server-config:/central-config
        # By default the JHipster Registry runs with the "dev" and "native"
        # Spring profiles.
        # "native" profile means the filesystem is used to store data, see
        # http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html
        environment:
            - SPRING_PROFILES_ACTIVE=dev,native
            - SECURITY_USER_PASSWORD=something
            - JHIPSTER_REGISTRY_PASSWORD=something
            - JHIPSTER_LOGGING_LOGSTASH_ENABLED=true
            - JHIPSTER_LOGGING_LOGSTASH_HOST=jhipster-logstash
            - JHIPSTER_METRICS_LOGS_ENABLED=true
            - JHIPSTER_METRICS_LOGS_REPORTFREQUENCY=60
            # - GIT_URI=https://github.com/jhipster/jhipster-registry/
            # - GIT_SEARCH_PATHS=central-config
        ports:
            - 8761:8761

Answer 1

我在窗户/码头上也有同样的问题。

解决方案是重新启动Docker并再次测试它