Pages : 1
#1 Le 08/04/2016, à 09:39
- HPIR40
Docker injoignable, mais quelle galère
Bonjour
J'espère trouver de l'aide ici car c'est la premiere fois que je me lance dans l'installation de docker et sa configuration.
J'ai créé un serveur hôte virtualisé avec l'ip 172.16.0.85
J'ai installé loomio en suivant scrupuleusement le doc suivante:
https://github.com/loomio/loomio-deploy
Après l'installation voila l'iptable de la machine hôte
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
DOCKER-ISOLATION all -- anywhere anywhere
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ES TABLISHED
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain DOCKER (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.17.0.5 tcp dpt:4443
ACCEPT tcp -- anywhere 172.17.0.3 tcp dpt:smtp
Chain DOCKER-ISOLATION (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
voila d'autres infos:
docker network inspect bridge
[
{
"Name": "bridge",
"Id": "aa0db8b15657833e69e63a0619f7691f33a3b6b9c2f330ed966a3c1c11f45f84",
"Scope": "local",
"Driver": "bridge",
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "172.17.0.0/16"
}
]
},
"Containers": {
"218ace6a014b606fae6a696730b92d31574affb82f3b101f5d31c15a575e2878": {
"Name": "loomiodeploy_mailin_1",
"EndpointID": "095c25a7ee32ef3a2cbabcc8c2b4fd2792954915c6bfc53aa606b95c87b11dc6",
"MacAddress": "02:42:ac:11:00:03",
"IPv4Address": "172.17.0.3/16",
"IPv6Address": ""
},
"8efee0b463b4846aeb5c0479093bd4505050858b14e88c35e84df85996a1920f": {
"Name": "loomiodeploy_worker_1",
"EndpointID": "6d5f2759cce10c10e920b2b50b14c8f4e22ce25d5365755880b9c61fe7ca7b02",
"MacAddress": "02:42:ac:11:00:06",
"IPv4Address": "172.17.0.6/16",
"IPv6Address": ""
},
"b475d96388f7933cc43ae8deed10aa5363aea70c4592b85eb968c45bc5dabe1c": {
"Name": "loomiodeploy_db_1",
"EndpointID": "c1a3c6db115b7c65aed2661d2120cda04596b186194f5234aa3e3f5672e8f484",
"MacAddress": "02:42:ac:11:00:02",
"IPv4Address": "172.17.0.2/16",
"IPv6Address": ""
}
},
"Options": {
"com.docker.network.bridge.default_bridge": "true",
"com.docker.network.bridge.enable_icc": "true",
"com.docker.network.bridge.enable_ip_masquerade": "true",
"com.docker.network.bridge.host_binding_ipv4": "0.0.0.0",
"com.docker.network.bridge.name": "docker0",
"com.docker.network.driver.mtu": "1500"
}
}
]
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8efee0b463b4 loomio/loomio "bundle exec rake job" 3 days ago Up 26 minutes loomiodeploy_worker_1
218ace6a014b loomio/mailin-docker "/bin/sh -c 'mailin -" 3 days ago Up 26 minutes 0.0.0.0:25->25/tcp loomiodeploy_mailin_1
b475d96388f7 postgres "/docker-entrypoint.s" 3 days ago Up 26 minutes 5432/tcp loomiodeploy_db_1
Bref, la je ne trouve vraiment ce qui coince car
si je tape https://172.16.0.85:4443 j'ai: La connexion a échoué
si je tape bien https://172.17.0.5:4443 j'ai: Le délai d'attente est dépassé
Moi qui croyais que c'était simple, ben grosse erreur
Merci pour votre aide
Dernière modification par HPIR40 (Le 08/04/2016, à 09:39)
Hors ligne
#2 Le 08/04/2016, à 10:54
- pires57
Re : Docker injoignable, mais quelle galère
Je ne pense pas que tu as suivi la doc, si tu regardes bien tu n'as aucun port en écoute sur ton container loomiodeploy_worker_1.
De plus, ici tu parles de port 4443 alors que dans la doc on ouvre le port 80 et 443, tu t'es planté quelque part.
Utilisateur d'Archlinux, Ubuntu et Kali Linux
Administrateur système et réseau spécialisé Linux.
LinkedIn
Hors ligne
#3 Le 08/04/2016, à 10:55
- HPIR40
Re : Docker injoignable, mais quelle galère
autre info je viens de refaire un docker docker-compose restart
docker inspect 8efee0b463b4
[
{
"Id": "8efee0b463b4846aeb5c0479093bd4505050858b14e88c35e84df85996a1920f",
"Created": "2016-04-04T09:57:44.8314169Z",
"Path": "bundle",
"Args": [
"exec",
"rake",
"jobs:work"
],
"State": {
"Status": "running",
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 729,
"ExitCode": 0,
"Error": "",
"StartedAt": "2016-04-08T09:28:10.7973566Z",
"FinishedAt": "2016-04-08T09:23:08.3095573Z"
},
"Image": "sha256:858856c40908c260ba83df70c1954589b10a7a60a4a54024d092f9d80b206bba",
"ResolvConfPath": "/var/lib/docker/containers/8efee0b463b4846aeb5c0479093bd4505050858b14e88c35e84df85996a1920f/resolv.conf",
"HostnamePath": "/var/lib/docker/containers/8efee0b463b4846aeb5c0479093bd4505050858b14e88c35e84df85996a1920f/hostname",
"HostsPath": "/var/lib/docker/containers/8efee0b463b4846aeb5c0479093bd4505050858b14e88c35e84df85996a1920f/hosts",
"LogPath": "/var/lib/docker/containers/8efee0b463b4846aeb5c0479093bd4505050858b14e88c35e84df85996a1920f/8efee0b463b4846aeb5c0479093bd4505050858b14e88c35e84df85996a1920f-json.log",
"Name": "/loomiodeploy_worker_1",
"RestartCount": 0,
"Driver": "aufs",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "",
"ExecIDs": null,
"HostConfig": {
"Binds": [
"/home/docker/loomio-deploy/certificates:/certificates:rw",
"/home/docker/loomio-deploy/attachments:/loomio/public/system/attachments:rw"
],
"ContainerIDFile": "",
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"NetworkMode": "default",
"PortBindings": {},
"RestartPolicy": {
"Name": "",
"MaximumRetryCount": 0
},
"VolumeDriver": "",
"VolumesFrom": [],
"CapAdd": null,
"CapDrop": null,
"Dns": [],
"DnsOptions": [],
"DnsSearch": [],
"ExtraHosts": null,
"GroupAdd": null,
"IpcMode": "",
"Links": [
"/loomiodeploy_db_1:/loomiodeploy_worker_1/loomiodeploy_db_1",
"/loomiodeploy_db_1:/loomiodeploy_worker_1/db",
"/loomiodeploy_db_1:/loomiodeploy_worker_1/db_1"
],
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"ShmSize": 67108864,
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": null,
"KernelMemory": 0,
"Memory": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": -1,
"OomKillDisable": false,
"PidsLimit": 0,
"Ulimits": null
},
"GraphDriver": {
"Name": "aufs",
"Data": null
},
"Mounts": [
{
"Source": "/home/docker/loomio-deploy/certificates",
"Destination": "/certificates",
"Mode": "rw",
"RW": true,
"Propagation": "rprivate"
},
{
"Source": "/home/docker/loomio-deploy/attachments",
"Destination": "/loomio/public/system/attachments",
"Mode": "rw",
"RW": true,
"Propagation": "rprivate"
}
],
"Config": {
"Hostname": "8efee0b463b4",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": [
"SMTP_DOMAIN=smtp.mondomaine.lan",
"HELPER_BOT_EMAIL=noreply@loomio.mondomaine.lan",
"SMTP_PASSWORD=password,
"RAILS_ENV=production",
"FAYE_URL=https://loomio.mondomaine.lan:4443/faye",
"CANONICAL_HOST=loomio.mondomaine.lan",
"REPLY_HOSTNAME=loomio.mondomaine.lan",
"DEVISE_SECRET=TwF1lJ3BUPwxDmYhgvF9YPapLu00+CCk4yv+WKo3ZkOvk9bBYqjdjBHIb2V+xctO",
"LOOMIO_SSL_CERT=/certificates/live/loomio.mondomaine.lan/fullchain.pem",
"DATABASE_URL=postgresql://postgres:password@db/loomio_production",
"SMTP_PORT=465",
"SMTP_SERVER=smtp.fai.net",
"LOOMIO_SSL_KEY=/certificates/live/loomio.mondomaine.lan/privkey.pem",
"SECRET_COOKIE_TOKEN=+8dJViEn84cfi6AGCTa7mMIfp+0wGPpFnpUTKTgVln9gyX+GNbRTVMIh5aTgE07H",
"TLD_LENGTH=2",
"SMTP_USERNAME=support@mondomaine.com",
"FORCE_SSL=1",
"SUPPORT_EMAIL=support@loomio.mondomaine.lan",
"PRIVATE_PUB_SECRET_TOKEN=rErbTlr6FFH6a3OrfCnRu43OvfQFNxA2YNiOzOEC4d+ybu6mGMFeQxUqIvEfxeFU",
"PATH=/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"RUBY_MAJOR=2.3",
"RUBY_VERSION=2.3.0",
"RUBY_DOWNLOAD_SHA256=ba5ba60e5f1aa21b4ef8e9bf35b9ddb57286cb546aac4b5a28c71f459467e507",
"RUBYGEMS_VERSION=2.6.2",
"BUNDLER_VERSION=1.11.2",
"GEM_HOME=/usr/local/bundle",
"BUNDLE_PATH=/usr/local/bundle",
"BUNDLE_BIN=/usr/local/bundle/bin",
"BUNDLE_SILENCE_ROOT_WARNING=1",
"BUNDLE_APP_CONFIG=/usr/local/bundle",
"REFRESHED_AT=2015-08-07"
],
"Cmd": [
"bundle",
"exec",
"rake",
"jobs:work"
],
"Image": "loomio/loomio",
"Volumes": {
"/certificates": {},
"/loomio/public/system/attachments": {}
},
"WorkingDir": "/loomio",
"Entrypoint": null,
"OnBuild": null,
"Labels": {
"com.docker.compose.config-hash": "abe38551b9b861c2333f31a2584a5a1c80fc083f3929f8bbe66a38cd5061d3a9",
"com.docker.compose.container-number": "1",
"com.docker.compose.oneoff": "False",
"com.docker.compose.project": "loomiodeploy",
"com.docker.compose.service": "worker",
"com.docker.compose.version": "1.6.2"
}
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "c8211089ff1fab5a4390f124bcc89fe6c1f4796f58f45893772352a451d059b6",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {},
"SandboxKey": "/var/run/docker/netns/c8211089ff1f",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "48e21b9ff013df182e202c50a36fc2e1333c9b2803b22181604427627881cb88",
"Gateway": "172.17.0.1",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "172.17.0.3",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"MacAddress": "02:42:ac:11:00:03",
"Networks": {
"bridge": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "2fbc66db52aae7bb9690a20a49e8044cb025010545e6b98766138e3da9c1e6af",
"EndpointID": "48e21b9ff013df182e202c50a36fc2e1333c9b2803b22181604427627881cb88",
"Gateway": "172.17.0.1",
"IPAddress": "172.17.0.3",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:11:00:03"
}
}
}
}
]
si je tape bien https://172.17.0.3:4443 j'ai: Le délai d'attente est dépassé
si je tape https://172.16.0.85:4443 j'ai: La connexion a échoué
Hors ligne
#4 Le 08/04/2016, à 14:11
- HPIR40
Re : Docker injoignable, mais quelle galère
Je ne pense pas que tu as suivi la doc, si tu regardes bien tu n'as aucun port en écoute sur ton container loomiodeploy_worker_1.
De plus, ici tu parles de port 4443 alors que dans la doc on ouvre le port 80 et 443, tu t'es planté quelque part.
merci donc c'est le service loomiodeploy_worker_1 sur l'ip 172.17.0.6 qui fait que loomio va fonctionner
ben c'est simple, je vais router l'ip de l'hote
Je regarde ça lundi, et te tiens au courant
merci
Hors ligne
#5 Le 11/04/2016, à 09:38
- HPIR40
Re : Docker injoignable, mais quelle galère
Bonjour
Bon je reviens vers vous car mon problème n'est toujours pas résolu
J'ai modifié les regles ip table pour tout accepter entre l'interface docker0 et eth0 (j'affinerai quand ça fonctionnera)
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
DOCKER-ISOLATION all -- anywhere anywhere
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain DOCKER (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.17.0.5 tcp dpt:smtp
Chain DOCKER-ISOLATION (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Voila le fichier de conf de mon docker
web:
image: loomio/loomio
env_file: ./env
ports:
- 80:3000
- 443:9292
links:
- db:db
environment:
- DATABASE_URL=postgresql://postgres:password@db/loomio_production
volumes:
- ./attachments:/loomio/public/system/attachments
- ./certificates:/certificates
worker:
image: loomio/loomio
env_file: ./env
links:
- db:db
environment:
- DATABASE_URL=postgresql://postgres:password@db/loomio_production
volumes:
- ./attachments:/loomio/public/system/attachments
- ./certificates:/certificates
command: "bundle exec rake jobs:work"
db:
image: postgres
volumes:
- ./pgdata:/pgdata
environment:
- POSTGRES_PASSWORD=password
- PGDATA=/pgdata
mailin:
image: loomio/mailin-docker
ports:
- "25:25"
links:
- web:web
environment:
- WEBHOOK_URL=http://web:3000/email_processor/
faye:
image: loomio/loomio-faye
env_file: ./env
ports:
- "4443:4443"
volumes:
- ./certificates:/certificates
Même pas une réponse aux pings quand je cherche
172.16.0.85:443 ou 172.16.0.85:4443 ou 172.16.0.85:80 ou 172.16.0.85:3000 ou 172.16.0.85:9292
c'est quoi ce bins?
Merci pour votre aide
Hors ligne
#6 Le 11/04/2016, à 10:02
- HPIR40
Re : Docker injoignable, mais quelle galère
j'ai recommencé à 0
voila mon iptable
/home/docker/loomio-deploy# docker-compose restart
Restarting loomiodeploy_faye_1 ... done
Restarting loomiodeploy_worker_1 ... done
Restarting loomiodeploy_mailin_1 ... done
Restarting loomiodeploy_web_1 ... done
Restarting loomiodeploy_db_1 ... done
root@docker:/home/docker/loomio-deploy# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
DOCKER-ISOLATION all -- anywhere anywhere
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain DOCKER (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:4443
ACCEPT tcp -- anywhere 172.17.0.4 tcp dpt:9292
ACCEPT tcp -- anywhere 172.17.0.4 tcp dpt:3000
ACCEPT tcp -- anywhere 172.17.0.5 tcp dpt:smtp
Chain DOCKER-ISOLATION (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
aucun des ports indiqués ne répond
et 2 minutes plus tard sans que je touche quoi que ce soit, voila mon iptable
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
DOCKER-ISOLATION all -- anywhere anywhere
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain DOCKER (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.17.0.5 tcp dpt:smtp
Chain DOCKER-ISOLATION (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
mais euuuuhhhh
Dernière modification par HPIR40 (Le 11/04/2016, à 10:31)
Hors ligne
#7 Le 11/04/2016, à 13:01
- pires57
Re : Docker injoignable, mais quelle galère
Vérifie les logs de tes containers.
Tu peut faire cela avec la commande
docker logs <container>
Utilisateur d'Archlinux, Ubuntu et Kali Linux
Administrateur système et réseau spécialisé Linux.
LinkedIn
Hors ligne
#8 Le 11/04/2016, à 14:31
- HPIR40
Re : Docker injoignable, mais quelle galère
Comme le problème persistait sur ma VM Locale sous virtualbox, je suis revenu à ma première VM sur mon serveur.
Voila les logs où je ne vois pas grand chose de compréhensible pour moi avec mes connaissance super reduite sur docker.
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bde94a3c6703 loomio/loomio-faye "/bin/sh -c 'thin --p" 7 days ago Up 3 hours 0.0.0.0:4443->4443/tcp loomiodeploy_faye_1
8efee0b463b4 loomio/loomio "bundle exec rake job" 7 days ago Up 3 hours loomiodeploy_worker_1
218ace6a014b loomio/mailin-docker "/bin/sh -c 'mailin -" 7 days ago Up 3 hours 0.0.0.0:25->25/tcp loomiodeploy_mailin_1
b475d96388f7 postgres "/docker-entrypoint.s" 7 days ago Up 3 hours 5432/tcp loomiodeploy_db_1
voila tous les logs
docker logs 8efee0b463b4
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-04T09:58:06+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
[Worker(host:8efee0b463b4 pid:1)] Exiting...
2016-04-04T12:31:39+0000: [Worker(host:8efee0b463b4 pid:1)] Exiting...
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-04T12:32:42+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-04T15:11:59+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
[Worker(host:8efee0b463b4 pid:1)] Exiting...
2016-04-08T08:06:41+0000: [Worker(host:8efee0b463b4 pid:1)] Exiting...
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-08T08:07:27+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
[Worker(host:8efee0b463b4 pid:1)] Exiting...
2016-04-08T09:23:02+0000: [Worker(host:8efee0b463b4 pid:1)] Exiting...
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-08T09:28:50+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
[Worker(host:8efee0b463b4 pid:1)] Exiting...
2016-04-11T08:39:32+0000: [Worker(host:8efee0b463b4 pid:1)] Exiting...
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-11T08:40:22+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
[Worker(host:8efee0b463b4 pid:1)] Exiting...
2016-04-11T08:49:42+0000: [Worker(host:8efee0b463b4 pid:1)] Exiting...
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-11T08:57:25+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
[Worker(host:8efee0b463b4 pid:1)] Exiting...
2016-04-11T09:47:46+0000: [Worker(host:8efee0b463b4 pid:1)] Exiting...
[Worker(host:8efee0b463b4 pid:1)] Starting job worker
2016-04-11T09:48:32+0000: [Worker(host:8efee0b463b4 pid:1)] Starting job worker
docker logs bde94a3c6703
/usr/local/bundle/gems/eventmachine-1.0.8/lib/em/connection.rb:411:in `block in start_tls': Could not find /certificates/live/loomio.mondomaine.lan/privkey.pem for start_tls (EventMachine::FileNotFoundException)
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/em/connection.rb:409:in `each'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/em/connection.rb:409:in `start_tls'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/backends/base.rb:152:in `initialize_connection'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/eventmachine.rb:1494:in `event_callback'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/eventmachine.rb:193:in `run_machine'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/eventmachine.rb:193:in `run'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/backends/base.rb:73:in `start'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/server.rb:162:in `start'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/controllers/controller.rb:87:in `start'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/runner.rb:200:in `run_command'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/runner.rb:156:in `run!'
from /usr/local/bundle/gems/thin-1.6.4/bin/thin:6:in `<top (required)>'
from /usr/local/bundle/bin/thin:16:in `load'
from /usr/local/bundle/bin/thin:16:in `<main>'
Thin web server (v1.6.4 codename Gob Bluth)
Maximum connections set to 1024
Listening on 0.0.0.0:4443, CTRL+C to stop
/usr/local/bundle/gems/eventmachine-1.0.8/lib/em/connection.rb:411:in `block in start_tls': Could not find /certificates/live/loomio.mondomaine.lan/privkey.pem for start_tls (EventMachine::FileNotFoundException)
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/em/connection.rb:409:in `each'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/em/connection.rb:409:in `start_tls'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/backends/base.rb:152:in `initialize_connection'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/eventmachine.rb:1494:in `event_callback'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/eventmachine.rb:193:in `run_machine'
from /usr/local/bundle/gems/eventmachine-1.0.8/lib/eventmachine.rb:193:in `run'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/backends/base.rb:73:in `start'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/server.rb:162:in `start'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/controllers/controller.rb:87:in `start'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/runner.rb:200:in `run_command'
from /usr/local/bundle/gems/thin-1.6.4/lib/thin/runner.rb:156:in `run!'
from /usr/local/bundle/gems/thin-1.6.4/bin/thin:6:in `<top (required)>'
from /usr/local/bundle/bin/thin:16:in `load'
from /usr/local/bundle/bin/thin:16:in `<main>'
Bon j'ai l'erreur
usr/local/bundle/gems/eventmachine-1.0.8/lib/em/connection.rb:411:in `block in start_tls': Could not find /certificates/live/loomio.mondomaine.lan/privkey.pem for start_tls (EventMachine::FileNotFoundException)
C'est quoi cette histoire de privkey.pem? ils n'en parlent nulle part dans le tuto.
docker logs 218ace6a014b
info: Mailin v3.0.3
info: Webhook url: http://web:3000/email_processor/
info: Log file: /var/log/mailin.log
info: Mailin Smtp server listening on port 25
warn: Webhook http://web:3000/email_processor/ seems invalid or down. You may want to double check the webhook url.
info: Mailin v3.0.3
info: Webhook url: http://web:3000/email_processor/
info: Log file: /var/log/mailin.log
info: Mailin Smtp server listening on port 25
warn: Webhook http://web:3000/email_processor/ seems invalid or down. You may want to double check the webhook url.
et enfin le dernier
docker logs b475d96388f7
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /pgdata ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
creating template1 database in /pgdata/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating collations ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
loading PL/pgSQL server-side language ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
syncing data to disk ... ok
Success. You can now start the database server using:
pg_ctl -D /pgdata -l logfile start
waiting for server to start....LOG: database system was shut down at 2016-04-04 09:33:41 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
done
server started
ALTER ROLE
/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
LOG: shutting down
waiting for server to shut down....LOG: database system is shut down
done
server stopped
PostgreSQL init process complete; ready for start up.
LOG: database system was shut down at 2016-04-04 09:33:43 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
WARNING: hash indexes are not WAL-logged and their use is discouraged
LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2016-04-04 12:31:45 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: database system was interrupted; last known up at 2016-04-04 12:31:47 UTC
LOG: database system was not properly shut down; automatic recovery in progress
LOG: invalid record length at 0/19C1B88
LOG: redo is not required
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2016-04-08 08:06:45 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2016-04-08 09:23:08 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2016-04-11 08:39:40 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: database system was interrupted; last known up at 2016-04-11 08:39:46 UTC
LOG: database system was not properly shut down; automatic recovery in progress
LOG: invalid record length at 0/19C1D48
LOG: redo is not required
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2016-04-11 09:47:54 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
Hors ligne
#9 Le 12/04/2016, à 10:11
- HPIR40
Re : Docker injoignable, mais quelle galère
up svp
merci
Hors ligne
#10 Le 12/04/2016, à 13:07
- pires57
Re : Docker injoignable, mais quelle galère
http://web:3000/email_processor/ seems invalid or down. You may want to double check the webhook url.
Je ne connais pas Loomio mais ce warning cause peut être une erreur.
Je vois également dans ma machine docker qu'il existe une image officiel de Loomio, pourquoi n'utilise tu pas celle ci?
docker search loomio
Utilisateur d'Archlinux, Ubuntu et Kali Linux
Administrateur système et réseau spécialisé Linux.
LinkedIn
Hors ligne
#11 Le 12/04/2016, à 14:00
- HPIR40
Re : Docker injoignable, mais quelle galère
ahhh ça m'interresse ça
tu as un tuto a me donner pour tout installer par ce biais?
comme je te l'ai dit je suis débutant sur docker donc j'ai besoin d'un coup de main, après ça ira bien quand je serais dégrossi
par avance merci
Hors ligne
Pages : 1