potiuk commented on issue #62405: URL: https://github.com/apache/airflow/issues/62405#issuecomment-4034341964
BTW, Breeze is nothing else than docker container that is started with docker -compose. The issue is with codespaces - not the container. Note also that generally speaking `breeze start-airflow` is a command that should be started OUTSIDE of the container - so starting it inside the codespaces container has never been intended. So what you are trying to do is to start another set of containers from within another started container - which is definitely not straigthforward and possibly even something that devcontainers prevent. If I were you - I woudl rather focus on finding out if you can pass START_AIRFLOW env variable from outside of the container when it starts - that might actually work better. Look at entrypoint_ci.sh - the whole logic of what happens when breeze contaier is entered is explained there - I believe some other variables will need to be set for START_AIRFLOW to work. You might take a look what happens when you actually start the container from out side `breeze start-airflow --verbose` will print the exact docker-compose commands, env variables set that are used when `breeze start-airflow` is run outside of the container. Possibly finding a good way to map those variables to be set when you start your codespaces is a good solution - this way you would have airflow started immediately when you start the container rather than trying to run `breeze start-airflow` inside it and trying to start yet-another set of containers via docker-in-docker. Probably this way will be easier. -- 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]
