You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this commit 074f2e7, the cli the image is using rolled forward to v2.
This image no longer works on raspberry pi.
I verified this by checking out v2.1.0 tag and rebuild the image locally -> working.
checking out v2.3.0 tag and rebuild the image locally -> ./backup.sh: line 95: /usr/bin/aws: cannot execute binary file: Exec format error
Is there a particular reason to move to v2 already? Maybe wait for AWS to release them in package manager? ref: aws/aws-cli#4947 (comment)
Docker hub doesn't have an arm build is also a problem but I guess I'll save it for now. (is it #5?)
BTW thanks for this great repo, I've researched a bit and by far this is the most satisfying despite the arm related issue.
The text was updated successfully, but these errors were encountered:
Since this commit 074f2e7, the cli the image is using rolled forward to v2.
This image no longer works on raspberry pi.
I verified this by checking out v2.1.0 tag and rebuild the image locally -> working.
checking out v2.3.0 tag and rebuild the image locally ->
./backup.sh: line 95: /usr/bin/aws: cannot execute binary file: Exec format error
Is there a particular reason to move to v2 already? Maybe wait for AWS to release them in package manager? ref: aws/aws-cli#4947 (comment)
Docker hub doesn't have an arm build is also a problem but I guess I'll save it for now. (is it #5?)
BTW thanks for this great repo, I've researched a bit and by far this is the most satisfying despite the arm related issue.
The text was updated successfully, but these errors were encountered: