Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
BoPeng opened this issue Mar 14, 2023 · 2 comments
Open

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

BoPeng opened this issue Mar 14, 2023 · 2 comments

Comments

@BoPeng
Copy link

BoPeng commented Mar 14, 2023

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.

@BoPeng BoPeng changed the title [BUG] Build error [BUG] command not found error during packer build Mar 14, 2023
@dcloud9
Copy link

dcloud9 commented Mar 20, 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?

@BoPeng
Copy link
Author

BoPeng commented Mar 20, 2023

Yes, I did just that and hit #23.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants