-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCS zarr datasets can only be opened with token='anon' from binder #14
Comments
Is this perhaps a case for hiding the exact data loading invocation in a Intake catalogue? :) |
In more detail, gcsfs is supposed to try the auth mechanisms in the following order (if not supplied), ['google_default', 'cache', 'cloud', 'anon'], meaning that if no credentials are found, you fall back to anon. Why this isn't working, I don't know, it'd be worthwhile finding out what kind of auth it thinks was successfully established. |
I have a feeling this is related to the automatic blocking of access to the metadata server which occurs in zero2jupyterhub-k8s. We override this here for pangeo.pydata.org. But probably not for binder. |
@rabernat - I just redeployed binder with the couldMetadata option set. Would you mind trying again? |
I am trying out these examples with the pangeo binder.
In pangeo.pydata.org, the following code works:
But in hub.binder.pangeo.io, it fails with
I find I need to do
which is significantly uglier and more complicated.
Can we somehow make anonymous tokens the default for gcsfs?
cc @martindurant, @jhamman
The text was updated successfully, but these errors were encountered: