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
Cloud-run Dockerfile installs Django 3, errors #60
Comments
The I'm going to look at merging |
Can I ask if there's a reason you're using the |
I’m using master. The Dockerfile in master clones the cloud-run branch. |
Ah, thank you. That's was an oversight. I moved the cloud run link to clone with master branch, as intended. |
Just so you know, I found a few issues with the cloud run environment/Dockerfile combination and I'm working through them in my spare time. If you're trying to get something running ASAP, I'd recommend using Heroku in the meantime. |
Hey there, we worked around those issues in a fork, as well adding a build file for our CI and a Helm deployment for Kubernetes. It's currently running on our cluster. Would offer to PR, but some of our changes may be specific to us. |
(We did use Heroku briefly for test purposes. It worked fine there!) |
Awesome! I'm going to dedicate some time to this later this week and will go through your fork, seeing what the best path to unifying them may be. Thanks for your patience with this. |
Great! The key changes in the Dockerfile were pegging the Dockerfile base to 3.7, the aforementioned branch switch and modifying the relative paths for copying the start scripts. Not sure whether that last one is required in cloud-run, but we needed it in our build. |
Built the project using a modified Dockerfile from deploy/google-cloud.
Got this error on deploy, when running the manage command:
Traced it to the Dockerfile cloning from the cloud-run repo branch, which installs Django >=2.2.2. Currently that's Django 3. Django 3 removed six.
The text was updated successfully, but these errors were encountered: