DEV.co
Open-Source Databases · oracle

docker-images

Official Oracle repository providing Dockerfiles and build instructions for containerizing Oracle commercial products (Database, WebLogic, SOA Suite, etc.) and open-source projects (GraalVM, NoSQL, OpenJDK). Users must source their own Oracle software licenses before building images; pre-built images with software included are available separately on Oracle Container Registry.

Source: GitHub — github.com/oracle/docker-images
7k
GitHub stars
5.4k
Forks
Shell
Primary language
UPL-1.0
License (Requires review (not clearly OSI))

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryoracle/docker-images
Owneroracle
Primary languageShell
LicenseUPL-1.0 — Requires review (not clearly OSI)
Stars7k
Forks5.4k
Open issues178
Latest releaseUnknown
Last updated2026-06-24
Sourcehttps://github.com/oracle/docker-images

What docker-images is

Shell-based Dockerfile collection maintained by Oracle for constructing container images across Oracle's product portfolio. Supports multi-product scenarios (Access Management, BI, FMW Infrastructure, etc.) with community contribution pathways. No official releases; continuous updates pushed to main branch.

Quickstart

Get the docker-images source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/oracle/docker-images.gitcd docker-images# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Oracle Database containerization in licensed environments

Organizations with valid Oracle Database licenses can use provided Dockerfiles to standardize database container builds for development, testing, and on-premises production workloads on Oracle Linux or compatible hosts.

GraalVM and OpenJDK container images

Open-source GraalVM CE and Oracle OpenJDK Dockerfile recipes simplify building lightweight JVM runtime images; suitable for polyglot applications and microservices requiring native image compilation or optimized Java runtimes.

Oracle FMW infrastructure containerization

Enterprises running Oracle WebLogic, SOA Suite, or other middleware can standardize container builds for integration platforms, message brokers, and service orchestration using official reference Dockerfiles.

Implementation considerations

  • Obtain valid Oracle product licenses before attempting builds; commercial software (Database, WebLogic, etc.) must be sourced separately and stored securely during container build.
  • Use Oracle Linux as base OS where possible; Dockerfiles are optimized for Oracle Linux but may support other distributions—test compatibility before production deployment.
  • Build images in isolated environments with secure handling of Oracle binaries; consider offline builds and artifact caching to reduce repeated downloads.
  • Pin Dockerfiles to specific Git commits rather than relying on main branch; lack of versioned releases means upstream changes may alter your image builds.
  • Review each product's Dockerfile individually; repository contains 20+ product subdirectories with varying complexity, maturity, and documentation depth.

When to avoid it — and what to weigh

  • No Oracle software licenses — Repository Dockerfiles require you to obtain and provide Oracle commercial software (e.g., Database, WebLogic binaries) during build. If you lack licenses, pre-built images from Oracle Container Registry still require license acceptance.
  • Need versioned releases and guaranteed stability — No official releases (latestRelease: n/a); changes pushed directly to main branch. Lacks semantic versioning or long-term support guarantees; pin to specific commits if stability is critical.
  • Require production-grade security scanning and compliance — Repository provides build recipes only; security posture of resulting images depends on base layers and manual configuration. No evidence of automated scanning, CVE tracking, or certified container image signing in provided data.
  • Lightweight or air-gapped environments — Oracle commercial product container images are typically large; building locally requires downloading substantial software binaries. Not suitable for minimal or edge deployments lacking Oracle infrastructure access.

License & commercial use

Licensed under Universal Permissive License v1.0 (UPL-1.0), a permissive OSI-approved license allowing use, modification, and distribution for both open-source and commercial purposes with minimal restrictions. Copyright retained by Oracle and affiliates. Dockerfile source code itself is freely usable; however, Oracle commercial products referenced within retain their own licensing terms.

UPL-1.0 permits commercial use of the Dockerfile collection itself. However, building and distributing container images of Oracle commercial products (Database, WebLogic, SOA Suite, etc.) requires separate Oracle product licenses. Redistributing pre-built images with Oracle software requires compliance with Oracle's licensing agreements. Consult Oracle licensing and legal counsel before commercial distribution. Open-source projects (GraalVM CE, OpenJDK, NoSQL) follow their own permissive or GPL licenses and may be used commercially with attribution.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

UPL-1.0 license itself contains no security warranties. Dockerfiles are publicly available source code; security posture depends on base image selection (Oracle Linux patches), Oracle software versions, and container runtime hardening. No evidence in provided data of automated security scanning, CVE tracking, or signed image verification. Build process requires handling Oracle software binaries securely (manage access, audit trails). Resulting images inherit Oracle product security patches; monitor Oracle security advisories independently. Container network policies and runtime security (AppArmor, SELinux) must be configured separately.

Alternatives to consider

Oracle Container Registry (OCR) pre-built images

Official pre-built container images with Oracle software included; eliminates local build complexity but requires Oracle account, license acceptance, and pull quota management. Simpler for small teams; less control over image customization.

Third-party Oracle product container images (Bitnami, etc.)

Community-maintained Dockerfiles for specific Oracle products (e.g., Database, WebLogic alternatives). May offer simpler build processes or additional tooling but differ from official Oracle recipes and may lack timely updates.

Manual Docker containerization or IaC tools (Terraform, Ansible)

Build container images from scratch using custom Dockerfiles and infrastructure-as-code for complete control over configuration. Higher initial effort but avoids dependency on Oracle's Dockerfile recipes; suitable for heavily customized environments.

Software development agency

Build on docker-images with DEV.co software developers

Start with the Dockerfile repository on GitHub. For pre-built images with software included, visit Oracle Container Registry. Ensure you have appropriate Oracle product licenses before building production images.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

docker-images FAQ

Do I need an Oracle license to use these Dockerfiles?
Yes, to build images of Oracle commercial products (Database, WebLogic, SOA Suite, etc.). Dockerfiles provide build recipes only; you must obtain and supply the actual Oracle software binaries. GraalVM CE, OpenJDK, and NoSQL have permissive licenses and do not require commercial licensing.
Can I modify and redistribute Dockerfiles?
Yes, UPL-1.0 permits modification and redistribution of Dockerfile source code. However, redistributing container images containing Oracle commercial software requires compliance with Oracle's product licenses. Consult Oracle licensing before redistribution.
How often are these Dockerfiles updated?
Unknown fixed schedule. Repository is actively maintained (last push 2026-06-24) with continuous updates to main branch. No versioned releases provided. Pin to specific Git commits for stability; monitor GitHub for breaking changes.
Are pre-built images available?
Yes, Oracle Container Registry (OCR) hosts pre-built images with software included. These require Oracle account login and license acceptance. Official Dockerfiles in this repository require local builds with your own software downloads.

Software developers & web developers for hire

DEV.co helps companies turn open-source tools like docker-images into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source databases stack.

Ready to containerize Oracle products?

Start with the Dockerfile repository on GitHub. For pre-built images with software included, visit Oracle Container Registry. Ensure you have appropriate Oracle product licenses before building production images.