testcontainers / testcontainers/testcontainers-java
[Feature]: Presto Module uses the outdated Docker Image of `ghcr.io/trinodb/presto` and needs to be updated to `prestodb/presto`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Module
Presto
Problem
-
Presto Module uses the outdated Docker Image of
ghcr.io/trinodb/prestoand needs to be updated toprestodb/presto. -
Refer to https://github.com/testcontainers/testcontainers-java/blob/1.19.8/modules/presto/src/main/java/org/testcontainers/containers/PrestoContainer.java and https://github.com/orgs/trinodb/packages/container/package/presto .
ghcr.io/trinodb/prestohas not been updated in 3 years. -
I'm confused by the instructions at https://java.testcontainers.org/modules/databases/presto/ .
This module is deprecated, use Trino module.
- The problem is, development of
prestohas been active, see https://hub.docker.com/r/prestodb/presto and https://github.com/prestodb/presto .
Solution
- Use
prestodb/prestoinstead ofghcr.io/trinodb/prestoinorg.testcontainers.containers.PrestoContainer.
Benefit
- This would obviously clarify the current situation regarding Presto. Presto is still maintained normally, so the corresponding testcontainers module should not be marked as deprecated.
Alternatives
- Maybe not. I'm not sure why
ghcr.io/trinodb/prestowas used initially.
Would you like to help contributing this feature?
No
Contributor guide
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 modules/presto/src/main/java/org/testcontainers/containers/PrestoContainer.java, the entry point identified in the issue, and compare its image configuration with the current Presto documentation and image references. Done means the module uses prestodb/presto and the documentation no longer presents the module's status misleadingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- databases, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100