-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed
Labels
kind/questionSomething requiring a response.Something requiring a response.
Description
If you suspect this could be a bug, follow the template.
-
What version of Dgraph are you using?
Dgraph version : v1.0.9
Commit SHA-1 : 22c13fc
Commit timestamp : 2018-10-02 16:45:53 -0700
Branch : HEAD -
Have you tried reproducing the issue with latest release?
No -
What is the hardware spec (RAM, OS)?
12GB RAM, Windows 10 1809 64-bit
Docker for Windows Edge Beta (Version 2.0.0.0-beta1-win75 (19925) Channel: edge 915f68b)
Windows Subsystem for Linux (latest Windows 10 1809)
Ubuntu 18.04 running in WSL with latest updates -
Steps to reproduce the issue (command/config used to run Dgraph).
- Install and setup Docker for Windows
- Set your C drive on Windows to be shared with Docker for Windows
- Make sure your C drive is mounted at
/c/and not/mnt/cin WSL:
sudo nano /etc/wsl.conf
# Now make it look like this and save the file when you're done:
[automount]
root = /
options = "metadata"
- Create the directory
/c/dgraphin WSL. - Create the dgraph container:
docker run -it -d -p 5080:5080 -p 6080:6080 -p 8080:8080 -p 9080:9080 -p 8000:8000 -v /c/dgraph:/dgraph --name dgraph dgraph/dgraph dgraph zero
- Dgraph fails to launch:
Dgraph version : v1.0.9
Commit SHA-1 : 22c13fce
Commit timestamp : 2018-10-02 16:45:53 -0700
Branch : HEAD
For Dgraph official documentation, visit https://docs.dgraph.io.
For discussions about Dgraph , visit https://discuss.dgraph.io.
To say hi to the community , visit https://dgraph.slack.com.
Licensed under Apache 2.0 + Commons Clause. Copyright 2015-2018 Dgraph Labs, Inc.
Setting up grpc listener at: 0.0.0.0:5080
Setting up http listener at: 0.0.0.0:6080
2018/10/29 04:17:47 Error while opening WAL store error: sync zw: invalid argument
While syncing directory: zw.
github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger.syncDir
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/db.go:461
github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger.helpRewrite
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/manifest.go:275
github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger.helpOpenOrCreateManifestFile
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/manifest.go:134
github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger.openOrCreateManifestFile
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/manifest.go:116
github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger.Open
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/db.go:234
github.com/dgraph-io/dgraph/dgraph/cmd/zero.run
/ext-go/1/src/github.com/dgraph-io/dgraph/dgraph/cmd/zero/run.go:181
github.com/dgraph-io/dgraph/dgraph/cmd/zero.init.0.func1
/ext-go/1/src/github.com/dgraph-io/dgraph/dgraph/cmd/zero/run.go:59
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).execute
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:702
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).ExecuteC
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:783
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).Execute
/ext-go/1/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:736
github.com/dgraph-io/dgraph/dgraph/cmd.Execute
/ext-go/1/src/github.com/dgraph-io/dgraph/dgraph/cmd/root.go:47
main.main
/ext-go/1/src/github.com/dgraph-io/dgraph/dgraph/main.go:24
runtime.main
/usr/local/go/src/runtime/proc.go:201
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1333
- Expected behaviour and actual result.
Dgraph should launch correctly.
Metadata
Metadata
Assignees
Labels
kind/questionSomething requiring a response.Something requiring a response.