Because we're using --volumes-from if there's a recording and then FreeSWITCH docker container changes before the cron job has been run it will not mount the recordings from the new container. That old container's volume should be still available though at sudo docker volume ls
Possible solution
Write another cron job which goes through all volumes (except for current volume) and does sync
Todo
Done
Documentation
Add option to disable uploads in Dockerrun.aws.json
Notes
Docker
Use volumes-from to mount volumes
$ sudo docker run -it --volumes-from 9cc3b6fdfc31 garland/aws-cli-docker /bin/sh
Possible Issues
Because we're using
--volumes-fromif there's a recording and then FreeSWITCH docker container changes before the cron job has been run it will not mount the recordings from the new container. That old container's volume should be still available though atsudo docker volume lsPossible solution
Write another cron job which goes through all volumes (except for current volume) and does sync
Todo
Done
Notes
Docker
Use volumes-from to mount volumes
Find the Container ID from the AWS Name tag