This repository was archived by the owner on Feb 24, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 24, 2026. It is now read-only.
Datastore emulator fails to start without project id property #355
Description
Environment details
- GCloud datastore emulator 2.1.0
- Google Cloud SDK 327.0.0
- OS type and version: NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" / MacOS Catalina 10.15.7 (19H15)
- Java version: OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.8+10) / OpenJDK Runtime Environment (build 11.0.7+10)
- Libs:
- https://github.com/GoogleCloudPlatform/spring-cloud-gcp:
org.springframework.cloud:spring-cloud-gcp-starter-data-datastore:1.2.5.RELEASE, I checked - same with the latest google-cloud-datastore:1.104.0google-cloud-core:1.93.7
Steps to reproduce
This version emulator fails to start without --project property
gcloud beta emulators datastore start
ERROR: (gcloud.beta.emulators.datastore.start) The required property [project] is not currently set.
You may set it for your current workspace by running:
$ gcloud config set project VALUE
or it can be set temporarily by the environment variable [CLOUDSDK_CORE_PROJECT]Starting emulator with Java code like this:
LocalDatastoreHelper.create(settings.getConsistency(), settings.getPort());Causes: no messages in logs, the application failed to call the Datastore then with I/O exceptions, i.e. curl doesn't work.
Workaround
Set env variable: CLOUDSDK_CORE_PROJECT with the projectId value
Questions
- Why
LocalDatastoreHelperdoesn't pass--projecton startup and doesn't expect this from the builder? - Shouldn't
LocalDatastoreHelper #startfail to start on this kind of errors?
Besides the outcomes of these questions, I would expect this class to fail to start or log something.
Activity
meredithslota commentedon Nov 15, 2021
I wonder if this is an issue with out-dated documentation — https://cloud.google.com/sdk/gcloud/reference/beta/emulators/datastore/start also declares that the
--projectflag isn't required, but maybe it is now. Are you setting the variables re: theenv-initcommand? It seems like it's expecting a variable like this: DATASTORE_PROJECT_ID=my-project-id (as per this page: https://cloud.google.com/datastore/docs/tools/datastore-emulator#automatically_setting_the_variables).artemptushkin commentedon Nov 16, 2021
@meredithslota I question here particularly
LocalDatastoreHelperclass and troubleshooting on its start-up issues.Consider it starts in an isolated environment without any env variable predefined, then
LocalDatastoreHelper startsfinishes but the method caller never knows that it failed to start due to missing an env variable, there is no log message.As well there is no method in builder to pass the project id explicitly
I propose:
It will make it clear as right now there is no clue to know why it failed to start when no env variable has been provided.
meredithslota commentedon Oct 10, 2022
There's a similar issue with the
LocalDatastoreHelpergoogleapis/google-cloud-java#12002 — @prash-mi can you include this with your investigation of the other issue?jainsahab commentedon Nov 23, 2022
@artemptushkin , Thanks for reporting this.
We have fixed this issue in this PR and is up for review. You can find the explanation and fix in the PR itself.
fix: #355 Explicitly passing --project argument when starting emulator (
chore(main): release 2.13.0 (#921)
chore: sync with main (#941)