Data Ingest Fix for new Linux AMI #830
Merged
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
… updated data-ingest EC2 user-data to not use buildkit in Docker build, updated Terraform version
nickchadwick-noaa
added
bug
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.
When the Linux Image Builder Pipeline was updated and fixed, the resulting new AMI broke the startup script for the Data Ingest EC2s. This is because the new AMI has a newer version of Docker, which handles the COPY commands in the Dockerfiles differently due to now using BuildKit in the Docker build process.
To fix this, I added an environment variable to disable buildkit.
Removed custom Rysylog install from the Linux Image Builder pipeline and updated rsyslog config to work with the older version of rsyslog already installed in the base AMI.
Updated Terraform block to work with new version of Terraform.