oci-image-pusher

Interactive CLI tool for building and pushing multi-arch Docker images to Oracle Cloud Infrastructure Container Registry (OCIR).

Features

• Guided setup for OCIR region, namespace, and image name
• Auto-discovers Dockerfiles in your project
• Builds multi-arch images (linux/amd64, linux/arm64) via docker buildx
• Tags images with both latest and git short rev (e.g. f85dbc5)
• Saves config to .oci-push.json for repeat use
• Handles Docker login to OCIR with proper username formatting (namespace/user)

Prerequisites

• Bun >= 1.0 (Node.js is not supported)
• Docker with buildx support
• An OCI account with access to OCIR
• An Auth Token for Docker login

Install

# Run directly without installing
bunx oci-image-pusher

# Or install globally
bun add -g oci-image-pusher
oci-push

Usage

Run the CLI from a directory that contains a Dockerfile:

bunx oci-image-pusher

The CLI walks you through the entire workflow interactively. Press Ctrl+C at any prompt to cancel.

Step 1: Configure OCIR (first run only)

On first run, the CLI prompts for three things:

1. OCIR Region — select from the list or enter a custom endpoint:

◆  Select OCIR Region
│  ○ Singapore (ap-singapore-1.ocir.io)
│  ○ Tokyo (ap-tokyo-1.ocir.io)
│  ○ Osaka (ap-osaka-1.ocir.io)
│  ○ Seoul (ap-seoul-1.ocir.io)
│  ○ Sydney (ap-sydney-1.ocir.io)
│  ○ Mumbai (ap-mumbai-1.ocir.io)
│  ○ US East - Ashburn (us-ashburn-1.ocir.io)
│  ○ US West - Phoenix (us-phoenix-1.ocir.io)
│  ○ Frankfurt (eu-frankfurt-1.ocir.io)
│  ○ Amsterdam (eu-amsterdam-1.ocir.io)
│  ○ London (uk-london-1.ocir.io)
│  ○ Custom endpoint
└

2. Tenancy Namespace — your OCI Object Storage namespace (find it at OCI Console → Profile → Tenancy → Object Storage Namespace):

◆  OCIR Tenancy Namespace
│  e.g. kx7mp2wrtqdf
└

3. Docker Image Name — the name for your image in the registry:

◆  Docker Image Name
│  my-app
└

After setup, the config is saved to .oci-push.json in the current directory. Subsequent runs load this file automatically and skip the setup:

┌  OCI Image Pusher
│
◇  Using saved config (.oci-push.json)
│  Endpoint:    ap-singapore-1.ocir.io
│  Namespace:   kx7mp2wrtqdf
│  Image:       my-app
│  Dockerfile:  Dockerfile
│
└

Step 2: Dockerfile discovery

The CLI scans the current directory (recursively) for files matching Dockerfile*. It skips node_modules and .git directories.

• One Dockerfile found — asks you to confirm:

  ◆  Use Dockerfile?
  │  Yes / No
  └

• Multiple Dockerfiles found — lets you pick one:

  ◆  Select a Dockerfile
  │  ○ Dockerfile
  │  ○ services/api/Dockerfile.prod
  │  ○ services/worker/Dockerfile
  └

Step 3: Docker login

The CLI checks ~/.docker/config.json for an existing login to the OCIR endpoint.

• Already logged in — skips ahead
• Not logged in — prompts for credentials:

  ◆  Docker Username (OCI email or federated user)
  │  [email protected]
  └
  ◆  Docker Password / Auth Token
  │  ▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪
  └

  The username is automatically formatted as namespace/user for OCIR authentication.

Step 4: Build mode

Choose what to do:

◆  What would you like to do?
│  ○ Build and push
│  ○ Build only
└

• Build and push — builds the multi-arch image and pushes it to OCIR
• Build only — builds locally without pushing (useful for testing)

Step 5: Build

The CLI runs docker buildx build with:

• Platforms: linux/amd64, linux/arm64
• Tags: latest and current git short rev (falls back to dev if not in a git repo)
• Build context: the parent directory of the selected Dockerfile

◇  Running: docker buildx build --platform linux/amd64,linux/arm64 \
     -t ap-singapore-1.ocir.io/kx7mp2wrtqdf/my-app:latest \
     -t ap-singapore-1.ocir.io/kx7mp2wrtqdf/my-app:f85dbc5 \
     --push -f Dockerfile .

Config file

The .oci-push.json file stores your project configuration:

{
  "endpoint": "ap-singapore-1.ocir.io",
  "namespace": "kx7mp2wrtqdf",
  "imageName": "my-app",
  "dockerfile": "Dockerfile"
}

To reconfigure, delete .oci-push.json and run the CLI again. This file is typically added to .gitignore since it may contain project-specific settings.

Supported Regions

| Region | Endpoint | |--------|----------| | Singapore | ap-singapore-1.ocir.io | | Tokyo | ap-tokyo-1.ocir.io | | Osaka | ap-osaka-1.ocir.io | | Seoul | ap-seoul-1.ocir.io | | Sydney | ap-sydney-1.ocir.io | | Mumbai | ap-mumbai-1.ocir.io | | US East (Ashburn) | us-ashburn-1.ocir.io | | US West (Phoenix) | us-phoenix-1.ocir.io | | Frankfurt | eu-frankfurt-1.ocir.io | | Amsterdam | eu-amsterdam-1.ocir.io | | London | uk-london-1.ocir.io | | Custom | Any *.ocir.io endpoint |

License

MIT