Allow LocalStack specific configuration of chmod on startup, remove DNS logic #34
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.
Motivation
DNS
The DNS rewrite logic was inactive since localstack/localstack-ext#2029.
With the removal we save binary space and reduce code complexity.
File system permissions
The approach to run chmod on
/var/task
,/tmp
and/opt
(even though some of them are conditional) taken with #27 has some issues, especially for startup performance with prebuild lambda images. Since with chmod, all the files in the directories (which change) will need to be copied into the upper layer in overlay2, this operation can take an significant amount of time to complete, which will reduce startup time drastically.We should let LocalStack decide when to apply this logic, and when we can avoid it.
Changes