Hasan-J opened a new pull request, #25251: URL: https://github.com/apache/airflow/pull/25251
Trying to make codespaces work. I faced 2 issues with that, fixed by the first 2 commits respectively. The issue with `local.yml` compose file was that it kept failing the build because of the mount source paths, if they don't exist on the host `Error response from daemon: invalid mount config for type "bind": bind source path does not exist`. I did some troubleshooting and the only thing I could come up with is that the docker-compose version is not the culprit here. I used the bootstrap image that codspaces use and were able to successfully bind mount non-existing dirs, so it could be something with the node app they use to get everything up and running? Side inquiry, I was initially confused as to what's the actual purpose for spinning up a codespace instance. Is it so we could mainly have testing env similar to CI and do only breeze tasks after you have done some changes somewhere else? or is it supposed to be a complete development env (similar to local on your machine) so you can create local virtual environmensts and launch different breeze configs? This question comes up after I realized that in the codespace instance you'd have: - `/opt/airflow` containing only the needed mounts from `local.yml`, with no `.git` dir. - `/workspaces/airflow` with the full code base and `.git` dir > Note: The changes in local.yml are just temp and only to get the codespace instance to run, I'm hoping to discuss it further in order to find a better solution -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
