-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Mojo cannot be installed in a Docker container because AUTH_KEY is deprecated #2265
Comments
Thanks, @phueac for your feedback. The recent client side changes in the auth flow change is a bug and we are working to fix this by the next release. I will forward you feedback on the remaining items to our internal teams. |
+1, this also seems to be a blocker for installing |
I blogged about using Docker to run Mojo with auto-generated authentication keys. It's a quick fix for those who need to bypass authentication. |
Also +1, I want to build nightly docker images for mojo nightly in github ci. If AUTH_KEY is deprecated I can't do this. I would really like to use mojo nightly and participate in contributing, however this can be a blocker. |
Issue description
I am trying to install and use Mojo within a Docker container. Your blog post at https://www.modular.com/blog/how-to-setup-a-mojo-development-environment-with-docker-containers indicates this can be does by passing an AUTH_KEY into the container during build. But it looks like this authentication method was deprecated in a recent update to the Modular CLI?
It seems from your example at https://github.com/modularml/mojo/tree/main/examples/docker that an auth key is still expected to build a Docker image. I found by trial and error that supplying a made-up string of random characters as the key allowed the Docker build to succeed.
Perhaps you need to update the blog post and Docker example to reflect the deprecation of the AUTH_KEY method?
As a side note, it is kind of sketchy to require a login to your proprietary system before even being able to download and try out your tools. How are you going to convince Python developers who are used to a completely open ecosystem to adopt this?
Steps to reproduce
Version Info
The text was updated successfully, but these errors were encountered: