Add AWS source block to Packer config #53
+84
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rin-skylight
reviewed
Mar 3, 2025
There was a problem hiding this comment.
This script does fundamentally the same thing as our existing post-install.sh. It seems that the only difference is the addition of the sudo command. Can you elaborate on this? I'd like to keep us from having to maintain multiple versions of essentially the same file, if possible.
There was a problem hiding this comment.
thank you for the review, @rin-skylight Our default post-install.sh fails when building the AWS Ubuntu VM because it does not have root permissions to perform package installations and file modifications. when I run with our default I usually run into this error message, hence the addition of sudo ,
==> iso.amazon-ebs.aws-ami: Provisioning with shell script: scripts/aws-post-install.sh
iso.amazon-ebs.aws-ami: post-install
iso.amazon-ebs.aws-ami: Reading package lists...
==> iso.amazon-ebs.aws-ami: E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
==> iso.amazon-ebs.aws-ami: E: Unable to lock directory /var/lib/apt/lists/
==> iso.amazon-ebs.aws-ami: curl: (23) Failure writing output to destination
==> iso.amazon-ebs.aws-ami: chmod: cannot access '/etc/apt/keyrings/docker.asc': No such file or directory
==> iso.amazon-ebs.aws-ami: tee: /etc/apt/sources.list.d/docker.list: Permission denied
==> iso.amazon-ebs.aws-ami: E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
iso.amazon-ebs.aws-ami: Reading package lists...
==> iso.amazon-ebs.aws-ami: E: Unable to lock directory /var/lib/apt/lists/
==> iso.amazon-ebs.aws-ami: W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
==> iso.amazon-ebs.aws-ami: W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)
==> iso.amazon-ebs.aws-ami: E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
==> iso.amazon-ebs.aws-ami: E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
EmmanuelNwa247
force-pushed
the
Emmanuel/Cloud-source
branch
from
ff53698 to
f1c2d69
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR Includes
Updated the ubuntu.pkr.hcl config file, adding an Amazon source and build block.
Included an aws-post-install script for post-installation steps specific to Amazon AMI VM builds.
Testing
Testing Instructions:
Ensure your AWS credentials are configured in your local environment.
Navigate to Directory: Go to the
utilsdirectory.Build AWS AMI: Run the following command to build the AWS AMI
./build.sh dibbs-ecr-viewer v2.0.0-betaGo to the AMI section in the AWS console and verify the newly built AMI.
Use the newly built AMI to launch an EC2 instance.
Open the inbound rules of your new instance to allow traffic from anywhere on port 3000.
Copy the public IPv4 address of the instance and paste it in your browser at
http://<your-instance-ip>:3000.