docker-library / docker-library/tomcat
Can an entrypoint be provided for Java truststore set-up?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 635
- Forks
- 744
- PR merge metrics
- No merged PRs in 30d
Description
#303 disabled the upstream entrypoint, which is __cacert_entrypoint.sh (at least in eclipse-temurin:8-jdk-jammy). This script can help set up the Java truststore. Can the functionality be reintroduced? It seems to me like setting up the truststore before Tomcat start-up would be a common use case. The script even acknowledges and deals with the issue for which it was bypassed:
#!/usr/bin/env bash
# Sheband needs to be `bash`, see https://github.com/adoptium/containers/issues/415 for details
However, I just found a recent change that switches this to sh again.
#!/usr/bin/env sh
# Converted to POSIX shell to avoid the need for bash in the image
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Tomcat image entrypoint change from #303 and compare the referenced __cacert_entrypoint.sh in eclipse-temurin:8-jdk-jammy with the POSIX-shell revision linked in the issue. Trace how the entrypoint runs before Tomcat startup and determine how Java truststore setup could be exposed without restoring the bypassed behavior. Done means the requested truststore setup functionality works in the affected image and its startup behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, shell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100