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
I commented on #10 but it is better create a a separate ticket.
When building the AIM using packer, I received the following error message:
amazon-ebs:
amazon-ebs: Installed:
amazon-ebs: gmp-devel.x86_64 1:6.0.0-15.amzn2.0.2
amazon-ebs:
amazon-ebs: Complete!
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: -bash: R: command not found
==> amazon-ebs: Stopping the source instance...
amazon-ebs: Stopping instance
==> amazon-ebs: Waiting for the instance to stop...
==> amazon-ebs: Deregistered AMI RStudio, id: ami-05f01cda1769bdda5
==> amazon-ebs: Creating AMI RStudio from instance i-07f8e50089b6938c7
amazon-ebs: AMI: ami-06b15831e898498fa
==> amazon-ebs: Waiting for AMI to become ready...
This looks like the same error that was fixed by a PR before, but maybe the version of libcurl is changed again.
The text was updated successfully, but these errors were encountered:
BoPeng
changed the title
[BUG] Build error
[BUG] command not found error during packer build
Mar 14, 2023
@BoPeng - yes, also hit us. Solution yet again is to bump to latest version of libcurl-devel-7.88.1.
I think it'll better not to pin any specific version as it seems to work with latest version every time we hit this issue?
I commented on #10 but it is better create a a separate ticket.
When building the AIM using packer, I received the following error message:
This looks like the same error that was fixed by a PR before, but maybe the version of libcurl is changed again.
The text was updated successfully, but these errors were encountered: