Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[RESOLVED] First run of container always exits with status 135 when local data volume resides within Dropbox folder hierarchy #1
When starting a container for the very first time, it always exits with status 135.
If you bring the container down and then up again, it'll be fine.
Nothing is written to the console.log, crash.log, error.log or sasl-error.log files.
referenced this issue
Sep 26, 2016
added a commit
Sep 28, 2016
Finally found the cause!
It seems to be that if you run the container with the /var/lib/actordb volume mounted somewhere within a Dropbox folder, it'll "Exit 135" when creating the lmdb and lmdb-lock files.
Not something my container or ActorDB can possibly ever address.
Just don't mount the container's /var/lib/actordb volume into a Dropbox folder, even during development!