trino

Apps

docker pull reg.mini.dev/trino

Apps

Updated 8 hours ago

docker pull reg.mini.dev/trino

Trino Overview

Secure your stack with a hardened Trino image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Trino is a distributed SQL query engine designed for fast, interactive analytic queries against data sources of all sizes ranging from gigabytes to petabytes.

Try It Out

Take the Minimus Trino image for a test run by deploying it on Kubernetes with Helm and executing a query against the built-in sample data.

Prerequisites

A running Kubernetes cluster (v1.21 or higher is recommended)
Helm v3.8 or higher for OCI support (Installation instructions)
kubectl installed and configured

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Add Repository to your Local Client

Add the Helm chart to your local Helm client.

helm repo add trino https://trinodb.github.io/charts
helm repo update

Step 3: Override Chart Defaults

Save the following to a values.yaml file in your working directory to override the defaults:

image:
  registry: reg.mini.dev
  repository: trino
  tag: latest
server:
  workers: 1

coordinator:
  resources:
    requests:
      memory: "2Gi"
      cpu: "1"
  startupProbe:
    timeoutSeconds: 5
    periodSeconds: 5
    failureThreshold: 100
  livenessProbe:
    initialDelaySeconds: 120
    periodSeconds: 10
    timeoutSeconds: 5
    failureThreshold: 6
  readinessProbe:
    initialDelaySeconds: 120
    periodSeconds: 10
    timeoutSeconds: 5
    failureThreshold: 6

Note the recommended pull policy for Minimus images.

In your working directory, check that the Helm chart is set to pull the Minimus image:

helm template my-trino-cluster trino/trino -f values.yaml | grep image:

Step 4: Deploy Trino

Run the following command from your working directory, where the values.yaml is located:

helm install my-trino-cluster trino/trino \
  --namespace trino \
  --create-namespace \
  -f values.yaml

Wait for all pods to be ready. Trino's JVM can take a couple of minutes to initialize, so watch until the READY column shows 1/1 for every pod:

kubectl -n trino wait --for=condition=ready pod -l app.kubernetes.io/name=trino --timeout=300s

Verify with:

kubectl -n trino get pods

Step 6: Connect to Trino

Once the pods are ready, connect to the coordinator pod and query the built-in tpch sample catalog using the Trino CLI that ships inside the container:

kubectl -n trino exec deploy/my-trino-cluster-trino-coordinator -- trino --execute "SELECT count(*) FROM tpch.tiny.nation"

You should see 25 rows returned. Explore additional tables under tpch.tiny to verify the cluster is working. For more configuration options such as adding catalogs, tuning JVM memory, and scaling workers, see the Trino Helm chart documentation.

Clean Up

Uninstall the deployment and delete the namespace:

helm uninstall my-trino-cluster -n trino
kubectl delete namespace trino

Technical Considerations

The Trino image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Trino built by Minimus:

For security reasons, the Minimus image includes only 5 of the 54 plugins in the public image. The plugins included by default operate entirely within the Trino JVM or use the local filesystem. The plugins excluded by default require external databases, cloud SDKs, or network endpoints to function.

To add plugins to your Trino image, create a private image using Creator. Dockerfile is not recommended because Trino plugins are tightly coupled to the exact server build. Learn more about Trino plugins
Runs as non-root by default for a security-first approach that protects against privilege escalation attacks.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.