-
Notifications
You must be signed in to change notification settings - Fork 14.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
Error in setting up the development environment following the docs for VS code #18849
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
M1 has some issues indeed. I believe the problem might be that MySQL still does not have ARM image. |
But If you managed to fix or at least improve some of those descriptions - feel free! |
Sure @potiuk I will add some improvements. One more thing I forgot to add to this issue: Following is the CI image information when running above command:
However i got the below message when running ./breeze flags
I expected ./breeze to start with sqlite by default but it starts with mysql. Am I missing something? |
Some of the parameters (like backend) are "saved" from the previous run and persisted (so that you can run "last used" configuration with just It is described here https://github.com/apache/airflow/blob/main/BREEZE.rst#choosing-different-breeze-environment-configuration
|
This support is mostly for the developers, not for CI full chain yet. It has several limitations: * no MySQL client support * no MsSQL client support * no CI tests yet What is implemented: * automated detection of ARM/AMD architecture when building and running breeze * automated cache refresh on CI for ARM/AMD Currently only development (ghcr.io) images are supported for ARM. Fixes: apache#18849 Fixes: apache#17494 Relates to: apache#15635 The images published in DockerHub for now are AMD64 only. We will run development with M1 images for some time and later we will likely make our DockerHub images multi-platform as well. Also Hadolint does not have ARM images yet so we had to disable it and we should re-enable it back after the support is added. See hadolint/hadolint#411
This support is mostly for the developers, not for CI full chain yet. It has several limitations: * no MySQL client support * no MsSQL client support * no CI tests yet What is implemented: * automated detection of ARM/AMD architecture when building and running breeze * automated cache refresh on CI for ARM/AMD Currently only development (ghcr.io) images are supported for ARM. Fixes: #18849 Fixes: #17494 Relates to: #15635 The images published in DockerHub for now are AMD64 only. We will run development with M1 images for some time and later we will likely make our DockerHub images multi-platform as well. Also Hadolint does not have ARM images yet so we had to disable it and we should re-enable it back after the support is added. See hadolint/hadolint#411
Describe the issue with documentation
https://github.com/apache/airflow/blob/main/CONTRIBUTORS_QUICK_START.rst#setup-and-develop-using-visual-studio-code
I am following the steps on the above page to set up the development environment. however, running the
pyenv install 3.8.5
in Apple M1 chip MacOS Big Sur runs into an error similar to the issue mentioned in the below StackOverflow linkhttps://stackoverflow.com/questions/65457674/unexpected-output-of-arch-on-osx-using-mac-m1-installing-elastic-beans
How to solve the problem
I am not sure how to solve this issue, but i used higher version of python 3.8.10 that is supported in M1 chip Apple MacOS Big Sur to solve the issue for time being.
Anything else
Further following the steps in this documentation, i got docker container up and running. however, if i try to reset the db, i get error saying
sqlalchemy.exc.OperationalError: (MySQLdb._exceptions.OperationalError) (1130, "Host 'docker-compose_airflow_run_718f404eac1d.docker-compose_defau' is not allowed to connect to this MySQL server")(Background on this error at: http://sqlalche.me/e/13/e3q8)
I am not sure why if i am running into this issue.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: