Unable to start chronograf via docker-compose

[craigwillis85]

Hi

I have just cloned the repo and run the ./sandbox up script.

But in looking at Chronograf, I see the following:

time="2018-03-23T17:33:06Z" level=error msg="Unable to open boltdb; is there a chronograf already running? invalid argument" component=boltstore

I'm running Docker version 18.01.0-ce, build 03596f5 on Mac OS X 10.12.6

Kapacitor also gives and error, which is likely related:

ts=2018-03-23T17:33:06.239Z lvl=error msg="encountered error" service=run err="open server: open service *storage.Service: open boltdb @ \"/var/lib/kapacitor/kapacitor.db\": invalid argument" run: open server: open service *storage.Service: open boltdb @ "/var/lib/kapacitor/kapacitor.db": invalid argument

[timhallinflux]

@craigwillis85 -- do you have any of the TICK stack components already running locally? or do you have anything running which is using ports 8086, 8088, 9092?

It seems that the underlying boltDBs which are using by both Chronograf and Kapacitor aren't able to start or are simply not contactable on your system. This is usually the problem.

the boltDBs are actually being written into your local file system, outside of the container. So, if you don't have write access to the point in the file system where we attempt to create them... I can see this being a problem as well. The location for these is ./<component_name/data so if you are sym-linking or doing something else to setup the sandbox commmands, this might create a situation where we cannot create that directory.

Perhaps we should be using the user's home directory and creating these within something like: ~/.sandbox/<component_name>/data

[craigwillis85]

@timhallinflux there is no other part of the tick stack running on those ports (docker-compose doesn't complain that there is)

I have tried the permissions as well, even chmod 777 the relevant folders, but nothing has worked

Can you confirm that this actually is working (maybe checkout the repo and run the ./sandbox up and see if it works)

[mikemix]

The sad part is the docker-compose file is using the latest tag instead of stable version, 1.4, 1.5 etc.

[timhallinflux]

Hi @mikemix -- why is using latest sad? That tag represents the latest, stable official released bits. We don't include the nightlies within the latest tag.

[TheKaterTot]

Hey @craigwillis85! This issue has been seen before. Check out issues #1 and #5. It looks like the version of Docker as well as whether you're using Docker Toolbox can affect this.

[timhallinflux]

@mikemix -- can you please provide your insight on the latest tag?

@craigwillis85 -- did this get you past the issue?