Reviewing main.tf for getting airflow setup
Here is a pastebin to my current
Currently I've noticed these issues:
- Stopping my workspace doesn't always stop the containers it created for airflow. I noticed this when I ssh into my server where I have Coder hosted with docker-compose and ran
- I'm still figuring out how to mount everything to the same source root so that I can edit my dags in the code-server.
- I noticed that code-server will be unhealthy sometimes and it's random. Currently the fix for this is to stop everything with
- Lastly, I have everything on the same network and when I run
The containers I created are based on this https://airflow.apache.org/docs/apache-airflow/2.6.2/docker-compose.yaml since I couldn't get DinD working as expected with permission issues.
main.tf file that I've been editing to get Airflow setup. (https://pastebin.com/msYXw1eU). Currently I've noticed these issues:
- Stopping my workspace doesn't always stop the containers it created for airflow. I noticed this when I ssh into my server where I have Coder hosted with docker-compose and ran
docker ps after stopping my workspace that uses that template.- I'm still figuring out how to mount everything to the same source root so that I can edit my dags in the code-server.
- I noticed that code-server will be unhealthy sometimes and it's random. Currently the fix for this is to stop everything with
docker stop ${docker ps -a} on my server and re-run coder. Also then deleting the workspace and creating a new one sometimes helps.- Lastly, I have everything on the same network and when I run
curl -v postgres inside the code-server terminal on that workspace it uses the wrong IP address. I can confirm that it is on the same network by using curldocker command to inspect the containers host ip. The containers I created are based on this https://airflow.apache.org/docs/apache-airflow/2.6.2/docker-compose.yaml since I couldn't get DinD working as expected with permission issues.
