Hello! I wiped my docker env clear first and then ...
# help
p
Hello! I wiped my docker env clear first and then tried spinning up the docker-compose environment in the
deployments/compose
dir via
docker compose up -d
. it seems the lakefs-setup service/container isn’t working anymore. I cannot login to
127.0.0.1:8000
and type in the example creds once the dust settles if i run
docker logs -t lakefs-setup
I see:
Copy code
paulsingman@Pauls-MacBook-Pro compose % docker logs -t lakefs-setup
2021-08-25T06:32:26.669666212Z time="2021-08-25T06:32:26Z" level=info msg="search for configuration file .lakefs" func=<http://github.com/treeverse/lakefs/cmd/lakefs/cmd.initConfig|github.com/treeverse/lakefs/cmd/lakefs/cmd.initConfig> file="/build/cmd/lakefs/cmd/root.go:57" phase=startup
2021-08-25T06:32:26.678427901Z time="2021-08-25T06:32:26Z" level=fatal msg="invalid config" func=cmd/lakefs/cmd.initConfig file="cmd/root.go:93" error="bad configuration: missing required keys: [blockstore.type]" fields.file="" file="cmd/root.go:93" phase=startup
Seems like a config setting is missing, can someone confirm what the right setting should be?
y
Hey Paul. I'm looking into it
@Paul Singman, did you make any changes to your docker-compose file?
In particular, the blockstore type configuration has become mandatory in the recent release
p
🙈 actually forgot I did make changes to the docker-compose (tried an earlier version). Lemme point it back to the latest and see what happens
👍🏻 1
latest docker-compose results in the same error in
lakefs-setup
. you don’t get the same error?
y
Can you make sure you have to most up-to-date file from the master branch?
p
i confirm they are identical
y
Ok, I'm getting the same error in the lakefs-setup step. It seems we forgot to add the blockstore type there. Will post a PR.
😬 1
p
it works, ty!