New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logspout container won't start without route configuration #185
Comments
I noticed the same thing in the latest release |
Should be caused by the following. I'll get a fix for it. |
I'm having the same issue, having troubles getting started as the binary simply won't start. Any news on this? |
Check out my temporary workaround in dokku-logspout Essentially I always include a Not sure if this helps your specific issues but that's how I got the container to start for my use case. |
23d3c9f seems to remedy the crashing behavior EDIT: this is how i started the container
|
The following commits are included from gliderlabs/master: commit a415f5d Merge: d56f003 324db6e Author: Jose Diaz-Gonzalez <josegonzalez@users.noreply.github.com> Date: Fri Jul 1 12:14:40 2016 -0400 Merge pull request gliderlabs#203 from udacity/master ignore containers with unsupported log drivers commit 324db6e Author: Paul M Bauer <paul@bauer.codes> Date: Fri Jul 1 08:22:56 2016 -0700 ignore containers with unsupported log drivers trying to hit /logs for a container that does not support that endpoint results in the following error in that container's stdout "Error running logs job: configured logging reader does not support reading" commit d56f003 Merge: 685c7bc 00147aa Author: Jose Diaz-Gonzalez <josegonzalez@users.noreply.github.com> Date: Thu Jun 30 18:13:11 2016 -0400 Merge pull request gliderlabs#171 from selimekizoglu/exclude-by-label Exclude containers by label. commit 00147aa Author: Selim Ekizoglu <selimeki@gmail.com> Date: Fri Jul 1 00:31:01 2016 +0300 Ignore empty EXCLUDE_LABEL values commit e92c2a0 Author: Selim Ekizoglu <selimeki@gmail.com> Date: Fri Jul 1 00:00:16 2016 +0300 Fixed documentation commit 079e8ae Author: Selim Ekizoglu <selimeki@gmail.com> Date: Thu Jun 30 23:33:44 2016 +0300 Renamed environment variable defining the label commit 685c7bc Merge: 5cad24a ff57c7d Author: Jose Diaz-Gonzalez <josegonzalez@users.noreply.github.com> Date: Thu Jun 30 12:06:54 2016 -0400 Merge pull request gliderlabs#200 from digitalkaoz/master Make Build Script Extentable commit 7ed5fb4 Author: d-sekizoglu <d-sekizoglu@ziraatteknoloji.com> Date: Thu Jun 30 11:56:06 2016 +0300 Documentation added commit 5cad24a Merge: 97c8c67 3ffcd8e Author: Jose Diaz-Gonzalez <josegonzalez@users.noreply.github.com> Date: Wed Jun 29 16:30:02 2016 -0400 Merge pull request gliderlabs#199 from iron-io/module-help Some instructions and helper scripts for working on custom modules. commit 97c8c67 Merge: a923387 13d1129 Author: Jose Diaz-Gonzalez <josegonzalez@users.noreply.github.com> Date: Mon Jun 13 15:43:10 2016 -0400 Merge pull request gliderlabs#191 from goodeggs/reconnect-logs reconnect log stream unless container is dead commit 13d1129 Author: Bob Zoller <bob@zoller.us> Date: Wed Jun 8 12:07:34 2016 -0700 avoid duplicate pumps with mutex lock commit ff57c7d Author: Robert Schönthal <caziel@gmx.net> Date: Mon Jun 6 23:01:51 2016 +0200 Update Dockerfile commit 3ffcd8e Author: Travis Reeder <treeder@gmail.com> Date: Tue May 31 20:04:53 2016 -0700 Some help for working on custom modules. commit a923387 Author: Matt Aitchison <Matt@lanciv.com> Date: Thu May 26 15:41:51 2016 -0500 Fix for gliderlabs#193 commit 38fa4b7 Author: Matt Aitchison <Matt@lanciv.com> Date: Mon May 23 16:38:58 2016 -0500 bump commit 19fa188 Author: Matt Aitchison <Matt@lanciv.com> Date: Mon May 23 16:26:22 2016 -0500 fixed version and date... commit 72dada2 Author: Matt Aitchison <Matt@lanciv.com> Date: Mon May 23 16:24:53 2016 -0500 release prep commit a86151b Author: Matt Aitchison <Matt@lanciv.com> Date: Mon May 23 16:21:24 2016 -0500 Update chnagelog commit 118f322 Author: Bob Zoller <bob@zoller.us> Date: Thu May 19 13:22:11 2016 -0700 reconnect log stream unless container is dead commit 23d3c9f Author: Matt Aitchison <Matt@lanciv.com> Date: Thu May 19 11:34:37 2016 -0500 Quick fix for gliderlabs#185 commit 231ac0e Author: Dylan Meissner <dylanmei@gmail.com> Date: Tue May 17 13:41:02 2016 -0700 Add logspout-kafka module to README (gliderlabs#77) commit 457941d Author: Tony Nuzzi <nuzzis@sbcglobal.net> Date: Tue May 17 15:37:58 2016 -0500 Add support text and command to stream logs to Loggly (gliderlabs#186) commit 0175188 Author: R. Toma <rtoma@bol.com> Date: Tue May 17 22:35:07 2016 +0200 added link to the logspout-redis-logstash module (gliderlabs#172) Change-Id: I69df9d76f472e84116a8e1b5b9e0c3cb255fe663 commit 8e54dea Author: R. Toma <rtoma@bol.com> Date: Tue May 17 22:22:26 2016 +0200 Now using Alpine Linux 3.3 and GO 1.5.3, removed the "edge" package repo for building the official Docker image (gliderlabs#174) Change-Id: I62a7960748906c1f9f7609dfc849f5ce0ce436fb commit 1bfbc27 Author: Matt Aitchison <Matt@lanciv.com> Date: Tue May 17 15:07:47 2016 -0500 Fixes issue gliderlabs#183 commit b6acebc Author: Matt Aitchison <Matt@lanciv.com> Date: Thu May 12 23:20:35 2016 -0500 cleaned up setup method commit 67eaa00 Author: Matt Aitchison <Matt@lanciv.com> Date: Wed May 11 18:45:21 2016 -0500 fix RouteManager.Name() commit 90302f0 Author: Michael Hobbs <michaelshobbs@users.noreply.github.com> Date: Wed Apr 20 19:46:57 2016 -0700 update container name if we get a rename event. closes gliderlabs#144 (gliderlabs#180) * update container name if we get a rename event. closes gliderlabs#144 * revert to using event.ID commit 113e3b7 Author: Selim Ekizoglu <sekizoglu@thoughtworks.com> Date: Thu Mar 24 17:57:49 2016 +0200 Exclude containers by label. Closes gliderlabs#159
I'm trying to get started with logspout, but following any of the examples in the readme fails, seemingly because it requires a route to be provided as part of the "run" command when starting the container.
If I don't, I get an error:
The problem is I'm trying to connect it to a Splunk server, also in a container, but it means I have to be sure the splunk server has started before logspout, otherwise it will fail. Any ideas?
The text was updated successfully, but these errors were encountered: