Update Dockerfile to include missing Python dependency and ensure file copying #2003
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
… are being copied to the image, debian docker libpython3.11.so.1.0 library error fixed
… are being copied to the image, debian docker libpython3.11.so.1.0 library error fixed, added back comments
|
Thanks for your PR. I left a couple of comments. Basically you mention in your commit that you want to add python3 but in reality it seems you are doing a lot of more things in this change. |
|
Sorry it is my first pull request, I did switch the bottom lines of the docker file to the top and set the copy command to .. which means all, in order to copy all files to the docket image for the line switch it’s more about formatting only. |
|
Please answer in the dedicated fields above when you are ready :) |
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 pull request updates the Dockerfile to resolve a missing dependency issue that prevented Profanity from starting in the Docker container. Specifically:
These changes enable Profanity to build and run successfully within the Debian-based Docker container.
How to Test the Functionality
docker build -t profanity_test .
Run the Container:
docker run -it profanity_test /bin/bashNavigate to the Profanity Directory:
cd /usr/src/profanityStart Profanity:
./profanityVerify: