Victor Sanahuja
Victor Sanahuja
Maybe something change on docker over time, I'm not using this script anymore you can try to tweak this line: https://github.com/piscue/docker-backup-scripts/blob/aa76dc430d5f5592b1fc06c872a318213341f729/backup-volumes.sh#L7
the backups you have are docker backups. you should uncompress and check a docker save/restore reference. Sorry I didn't implement the restore part on this scripts
if you look for docker volume restore you'll find the reference
https://github.com/piscue/docker-backup-scripts/issues/6
Well, after doing some brew update/upgrades now works as expected
mmm, not sure. I've tried to see my Terminal history but it's not there anymore. The thing I know, for being able to update brew I was needed to reinstall...
any updates? we are also lacking `ddtrace` as the only library in order to unlock better performance in our applications
like me...
example of all the findings https://github.com/piscue/docker-backup-scripts/actions/runs/7467795693/job/20321989808?pr=17
@M1kep @npalm faced the same issue. I had a monitor that controls the amount of EC2 spawn and never honored the `runners_maximum_count`. I did check the code, I was about...