search

RLOpenCatalyst / Service_Workbench_Templates

Templates for AWS Service Workbench from Relevance Lab
7 stars 13 forks source link

[BUG] command not found error during packer build #22

Open BoPeng opened 1 year ago

BoPeng commented 1 year ago

I commented on https://github.com/RLOpenCatalyst/Service_Workbench_Templates/issues/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.

dcloud9 commented 1 year ago

@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?

BoPeng commented 1 year ago

Yes, I did just that and hit #23.