We could use UDP, which would avoid this problem, but also it causes issues if you have intermittent network issues, you will lose logs entirely. In both of these cases, your container doesn't launch. Or if it flat our rejects the connection:ĭocker run -log-opt syslog-address=tcp://localhost:1212 -log-driver=syslog nginxĭocker: Error response from daemon: Failed to initialize logging driver: dial tcp 127.0.0.1:1212: getsockopt: connection refused. $ docker run -log-opt syslog-address=tcp://:1212 -log-driver=syslog nginxĭocker: Error response from daemon: Failed to initialize logging driver: dial tcp 216.58.216.142:1212: getsockopt: connection timed out. I would say that having logs be delayed is optimal to not being able to start your server. You could have network issues to your syslog server, and this will stop your production apps from running. This is especially problematic in a production environment where you are trying to ship logs to a central place. If you try to start docker with a remote tcp syslog, which is currently unavailable, docker will fail to start.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |