2017-07-07 2 views
0

Exécution de Docker 1.9.1 sur OpenSuse 42.1 (impossible de mettre à niveau pour le moment mais également le même problème sur Docker 1.12).Port HTTP exposé mais ne répondant pas correctement

J'ai une image Docker qui expose une application Web sur le port 8080. Je peux ssh dans le conteneur et accéder à l'application correctement depuis l'intérieur du conteneur sur http://localhost:8080/.

je lance le conteneur à l'aide

docker run -p 10000:8080 ... 

et je me attends à l'application Web étant accessible soit sur

http://localhost:10000 or http://public-ip:10000 

Le port est ouvert mais la connexion est fermée immédiatement.

sudo netstat -nap|grep LISTEN|grep -v LISTENING|grep 1000 
root's password: 
tcp  0  0 :::10000    :::*     LISTEN  17375/docker-proxy 

Je peux telnet au port 10000 mais comme dit la connexion est fermée immédiatement

docker --version 
Docker version 1.9.1, build a34a1d5 
docker version 
Client: 
Version: 1.9.1 
API version: 1.21 
Go version: go1.4.2 
Git commit: a34a1d5 
Built: 
OS/Arch: linux/amd64 
Server: 
Version:  1.9.1 
API version: 1.21 
Go version: go1.4.2 
Git commit: a34a1d5 
Built:   
OS/Arch:  linux/amd64 

docker info (1.9) 
Containers: 23 
Running: 1 
Paused: 0 
Stopped: 22 
Images: 198 
Server Version: 1.12.6 
Storage Driver: devicemapper 
Pool Name: docker-8:2-1074640197-pool 
Pool Blocksize: 65.54 kB 
Base Device Size: 10.74 GB 
Backing Filesystem: xfs                                               
Data file: /dev/loop0                                                
Metadata file: /dev/loop1                                               
Data Space Used: 13.22 GB                                               
Data Space Total: 107.4 GB                                              
Data Space Available: 94.16 GB                                             
Metadata Space Used: 20.58 MB                                              
Metadata Space Total: 2.147 GB                                             
Metadata Space Available: 2.127 GB                                            
Thin Pool Minimum Free Space: 10.74 GB                                           
Udev Sync Supported: true                                               
Deferred Removal Enabled: false                                             
Deferred Deletion Enabled: false 
Deferred Deleted Device Count: 0 
Data loop file: /var/lib/docker/devicemapper/devicemapper/data 
WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device. 
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata 
Library Version: 1.02.136 (2016-11-05) 
Logging Driver: journald 
Cgroup Driver: systemd 
Plugins: 
Volume: local 
Network: null bridge host overlay 
Swarm: inactive 
Runtimes: oci runc 
Default Runtime: oci 
Security Options: seccomp 
Kernel Version: 4.11.8-200.fc25.x86_64 
Operating System: Fedora 25 (Server Edition) 
OSType: linux 
Architecture: x86_64 
Number of Docker Hooks: 2 
CPUs: 6 
Total Memory: 29.45 GiB 
Name: dev2.zopyx.com 
ID: DE7T:KEX4:UCRB:KOED:2DHE:3437:MYDS:LPQT:BBYO:SOQH:2EZL:VTYR 
Docker Root Dir: /var/lib/docker 
Debug Mode (client): false 
Debug Mode (server): false 
Registry: https://index.docker.io/v1/ 
Insecure Registries: 
127.0.0.0/8 
Registries: docker.io (secure) 


docker info (1.12) 
Containers: 23 
Running: 1 
Paused: 0 
Stopped: 22 
Images: 198 
Server Version: 1.12.6 
Storage Driver: devicemapper 
Pool Name: docker-8:2-1074640197-pool 
Pool Blocksize: 65.54 kB 
Base Device Size: 10.74 GB 
Backing Filesystem: xfs 
Data file: /dev/loop0 
Metadata file: /dev/loop1 
Data Space Used: 13.22 GB 
Data Space Total: 107.4 GB 
Data Space Available: 94.16 GB 
Metadata Space Used: 20.58 MB 
Metadata Space Total: 2.147 GB 
Metadata Space Available: 2.127 GB 
Thin Pool Minimum Free Space: 10.74 GB 
Udev Sync Supported: true 
Deferred Removal Enabled: false 
Deferred Deletion Enabled: false 
Deferred Deleted Device Count: 0 
Data loop file: /var/lib/docker/devicemapper/devicemapper/data 
WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device. 
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata 
Library Version: 1.02.136 (2016-11-05) 
Logging Driver: journald 
Cgroup Driver: systemd 
Plugins: 
Volume: local 
Network: bridge host overlay null 
Swarm: inactive 
Runtimes: runc oci 
Default Runtime: oci 
Security Options: seccomp 
Kernel Version: 4.11.8-200.fc25.x86_64 
Operating System: Fedora 25 (Server Edition) 
OSType: linux 
Architecture: x86_64 
Number of Docker Hooks: 2 
CPUs: 6 
Total Memory: 29.45 GiB 
Name: dev2.zopyx.com 
ID: DE7T:KEX4:UCRB:KOED:2DHE:3437:MYDS:LPQT:BBYO:SOQH:2EZL:VTYR 
Docker Root Dir: /var/lib/docker 
Debug Mode (client): false 
Debug Mode (server): false 
Registry: https://index.docker.io/v1/ 
Insecure Registries: 
127.0.0.0/8 
Registries: docker.io (secure) 

Quel pourrait être le problème ici?

+0

Utilisez-vous un volume quelconque avec le conteneur? –

+0

Aucun volume n'est impliqué ici – Jens

+0

Pouvez-vous poster des informations sur les dockers? – johnharris85

Répondre

0

Solution: le webservice se liait uniquement à 127.0.0.1 au lieu de 0.0.0.0