Installing Astronomer on your machine is really just the CLI. When you run astro airflow start, it creates containers, pulls images, and creates volumes etc that can eventually take up some space. A few cleanup methods:
You can use $ docker system prune to remove all unused objects.
If you’re working locally and want to stop all running containers and volumes while maintaining the underlying database, run astro airflow stop
The underlying database will persist in the docker volume
Run $ astro dev kill
This is the same as astro airflow stop but will stop local containers AND prune volumes for that project. It’s forcing a restart as fresh as you can get.
This includes clearing the database entirely (you won’t see prior DAG runs in the Airflow Web UI)
What version of the Astronomer CLI you’re using? Make sure you’re on latest (v0.23.3) in case you’re hitting any previous bugs. For install instructions, follow CLI Quickstart.
Can you try running $ astro dev kill instead? We deprecated the $ astro airflow kill command a few minor versions ago.
Give that a shot and let us know if you’re still running into trouble.
Sorry, @paola, I haven’t quite understood the recipe. Do the above really remove Airflow and Astronomer content from the computer?
My own interest is *repairing" an Astronomer installation. I must have accidentally deleted files and folders, and now have a folder containing subfolders “dags”, “logs” and “plugins” and no files at the top level. (No Dockerfile, for example) Nonetheless, surprisingly, I still get running containers linked to that folder. (Incidentally, what do you call the group the containers are in? An “app”?)
: