Transfer only contents of Kafka and ZooKeeper properties files #76
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
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.
I've been playing around with this library to investigate listener configurations (likely helpful to #63), but I am unable to run the tests in an environment with podman. It turns out that copying a
MountableFileto the containers preserves the user and group Ids from the host machine via an intermediate tar file. This fails with podman due to the chown command not being allowed.The change proposed here is to read the contents of the
MountableFileprior to copying into the container. This drops the user and group information, which should not be relevant.An additional change is to delay copying the Kafka properties until the container is starting, which allows for
withKraftandwithServerPropertiesto be called in any order.