Can't start Crate with mounted data directory

Expected behaviour

A Crate container with a mounted data volume should start.

Actual behaviour

The Crate server fails to start and provides a stack trace in the logs (see below).


OS X: version 10.11.4 (build: 15E65) version v1.11.1-beta10
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160510-111029.tar.gz
Most specific failure is: No error was detected
Your unique id is: 91F1470A-E551-4108-B33C-AD878B8F0E2B
Please quote this in all correspondence.

Steps to reproduce the behavior

Run this command:

‘docker run -p 4200:4200 -p 4300:4300 -v some-directory:/data crate’

The output is:

[2016-05-10 09:03:21,652][INFO ][node ] [Living Eraser] version[1.7.5], pid[1], build[${build/NA]
[2016-05-10 09:03:21,653][INFO ][node ] [Living Eraser] initializing …
[2016-05-10 09:03:22,009][INFO ][io.crate.plugin ] [Living Eraser] plugins loaded: [crate-aws, hfs snapshot]
[2016-05-10 09:03:22,137][INFO ][plugins ] [Living Eraser] loaded [crate-core], sites [crate-admin]
{1.7.5}: Initialization Failed …

  • ElasticsearchIllegalStateException[Failed to created node environment]
    FileSystemException[/data: Function not implemented]

Issue probably relates to: Can't start elasticsearch with mounted data directory - [f]stat[v]fs family of functions

Just FYI: this issue still applies to Docker for Mac Version 1.11.1-beta11 (build: 6974)

I’ve tried to reproduce and yes, it looks like this is likely the same issue as mentioned in the other post. We’re hoping to fix this soon, so please keep watching the changelog for a fix to #3099! Thanks for your help in making Docker for Mac awesome!

1 Like

This appears to be fixed with Version 1.11.2-beta15 (build: 9168) but there was no mention of this in release notes.