Closed preetmyob closed 8 months ago
Thanks for reporting. What’s the command parameters you use to run it? On Oct 19, 2023, at 5:14 PM, Preet Sangha (MYOB) @.***> wrote:
@okigan Just wanted to give a head up. We've been using the older (previous latest v0.29) and it's been working fine. However we have been getting errors with very docker version over this one.
These are the errors with "latest and v0.30" images
2023-10-18T21:50:36Z] Unable to find image 'okigan/awscurl:latest' locally
[2023-10-18T21:50:38Z] latest: Pulling from okigan/awscurl
96526aa774ef: Pull complete
9875af95546d: Pull complete
69babf7e971f: Pull complete
ba93e141e36c: Pull complete
f0588e5d3d11: Pull complete
026df7a0cea5: Pull complete
Digest: sha256:3b0d68b9e125f7c868de88aeab064dfa12fdbafffec1c6b7cf9cba510744fad3
[2023-10-18T21:50:42Z] Status: Downloaded newer image for okigan/awscurl:latest
[2023-10-18T21:50:44Z] Traceback (most recent call last):
[2023-10-18T21:50:44Z] File "/app/python-packages/bin/awscurl", line 8, in
This was on an amd64 platform. I think it might be related to the release of the linux/arm64 images
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Hi @okigan,
sorry our commend got hidden in the wall of text I posted. Here it is again.
docker run --rm -ti -v "$HOME/.aws:/root/.aws" -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_SECURITY_TOKEN -e AWS_PROFILE -e AWS_REGION okigan/awscurl:latest "${api_url_base}/api/rxxxxx"
where "${api_url_base}/api/rxxxxx"
is the URL
And as I said, reverting to okigan/awscurl:v0.29
doesn't have this issue.
@preetmyob please confirm if latest release resolve the issue
@preetmyob please confirm if latest release resolve the issue
Hey there @okigan
Yes Latest (v0.32) does indeed fix the problem. Thank you for your responsiveness in getting this fixed for us.
👍
@okigan Just wanted to give a head up. We've been using the older (previous latest v0.29) and it's been working fine. However we have been getting errors with every docker version over this one.
These are the errors with "latest and v0.30" images
This was on an amd64 platform, Amazon Linux 2 as the base OS
I think it might be related to the release of the
linux/arm64 images
reverting to v0.29 has resolved this issue.
the command line:
get OS Info