Open raymzag opened 2 years ago
Hi @raymzag, Thank you for submitting the issue. It was reproducible using the steps above.
We will take a look at this and prioritize a fix.
Hi @raymzag, This also seems to be a bug with respect to v1 and v2 both. Again, thank you for bringing this to our attention.
Also, a workaround this would be to use the following set of commands instead until a fix is shipped:
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
To add some more context here, the issue is specifically the usage of relative pathing. If you use the absolute paths for -i
and -b
, we'd expect the functionality to work.
The fix for the current issue will be to automatically expand the paths at runtime for the install script so they're properly stored in the aws bin file.
Thank you for looking into it!
Describe the bug
Followed the linux installation steps with
-i
and-b
option, but symlinks seem broken. I am unable to runaws
after install. It is failing with "No such file or directory"https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html
It seems similar issue has been reported in this thread here too. https://www.reddit.com/r/Ubuntu/comments/hdrfly/aws_cli_command_not_working_when_installed_local/fvn1umn/
Expected Behavior
can run aws command.
Current Behavior
Reproduction Steps
Possible Solution
./aws-cli/v2/2.5.2/bin/aws
this seems working when calling directly.Additional Information/Context
No response
CLI version used
V2
Environment details (OS name and version, etc.)
ubuntu:20.04