Phil Marius
09/06/2021, 10:11 AMGeorge Claireaux (Airbyte)
Phil Marius
09/06/2021, 10:33 AMPhil Marius
09/06/2021, 10:35 AMdocker-compose down -v and there’s no storage to do that evenGeorge Claireaux (Airbyte)
docker exec -it <container name/id> /bin/shPhil Marius
09/06/2021, 10:44 AM$ docker exec -it <id> /bin/shPhil Marius
09/06/2021, 10:44 AMHarshith (Airbyte)
/tmp/workspace in scheduler and delete all the old jobs or inside which you will find the logs file you can delete that. I hope this helps
To get into scheduler
1. docker ps - you will get all the containers
2. docker exec -it <id of scheduler> bash
3. cd /tmp/workspacePhil Marius
09/06/2021, 11:13 AMexec -it into the image
$ docker exec -it <id> /bin/sh
OCI runtime exec failed: write /tmp/runc-process448723027: no space left on device: unknownPhil Marius
09/06/2021, 11:14 AMdocker-compose down eitherHarshith (Airbyte)
Phil Marius
09/06/2021, 11:16 AMHarshith (Airbyte)
Phil Marius
09/06/2021, 11:21 AMPhil Marius
09/06/2021, 11:22 AM[DEPRECATED] Marcos Marx
docker airbyte-scheduler stop then echo "" > $(docker inspect --format='{{.LogPath}}' airbyte-scheduler and docker airbyte-scheduler start with that you should have space to execute the commands.Aaron Scott
11/09/2021, 7:04 PMdocker stop airbyte-scheduler
sudo echo "" > $(docker inspect --format='{{.LogPath}}' airbyte-scheduler)
docker start airbyte-scheduler
Then I could follow the the usual busybox instructions to delete the old logs from /data/ in the container.[DEPRECATED] Marcos Marx