Skip to content
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

Support for gs:// and s3:// directories #44

Open
alexgorbachev opened this issue Feb 14, 2019 · 2 comments
Open

Support for gs:// and s3:// directories #44

alexgorbachev opened this issue Feb 14, 2019 · 2 comments

Comments

@alexgorbachev
Copy link

Would it be possible to add a feature when gs:// or s3:// log_dir can be specified for Tensorboard to start? Assuming the environment is already authenticated to the GCP or AWS.
I'm running job in Google Cloud ML Engine and logs are in a GCS bucket. Also using JupyterLab inside a container on the cloud instances where this can be added too if supported by this package. chesterli29/jupyterlab_tensorboard#9 (comment)
cc @chaoleili

@diogoseca
Copy link

While this is still not working, you can start tensorboard from the Cloud Shell, and preview on port 6006 (or whatever port you use for running tensorboard).

However, it'd be nice to open tensorboard from the jupyterlab without this workaround.

@wookayin
Copy link

wookayin commented May 4, 2020

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants