https://github.com/pacificcommunity/ofp-sam-docker-images

This repository contains publicly available Docker images for various projects
https://github.com/pacificcommunity/ofp-sam-docker-images

docker image ofp sam

Last synced: about 1 month ago
JSON representation

This repository contains publicly available Docker images for various projects

• Host: GitHub
• URL: https://github.com/pacificcommunity/ofp-sam-docker-images
• Owner: PacificCommunity
• License: mit
• Created: 2025-02-06T08:16:06.000Z (4 months ago)
• Default Branch: main
• Last Pushed: 2025-03-26T22:05:02.000Z (about 2 months ago)
• Last Synced: 2025-03-26T23:20:33.175Z (about 2 months ago)
• Topics: docker, image, ofp, sam
• Language: Dockerfile
• Homepage:
• Size: 3.94 MB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
![Workflow Status](https://github.com/PacificCommunity/ofp-sam-docker-images/actions/workflows/build-and-push.yml/badge.svg)

For reproducibility, each top-level directory contains a Dockerfile and associated files to build a Docker image. The GitHub Actions workflow automatically builds and pushes these images to GitHub Container Registry (GHCR) under the `PacificCommunity` organisation.

The pushed images are available at:

https://github.com/orgs/PacificCommunity/packages

# Overview

This repository includes a GitHub Actions workflow that:

1. Detects changed top-level directories (e.g., `skj-2025/`, `yft-2025/`).

2. Builds Docker images for each changed directory.

3. Pushes them to GitHub Container Registry (GHCR) under the `pacificcommunity` organisation.

4. Either uses a user-specified version (provided via `workflow_dispatch`) or automatically increments the minor version if previous tags exist.

# Key Features

- **Auto-incrementing version**:

  - Scans GHCR for the highest existing tag (e.g., `v1.4` or `1.4`) and increments to `1.5`.

  - Defaults to `1.0` if no valid version is found or the package does not exist.

- **User-specified version**:

  - If you manually dispatch the workflow and enter a version (e.g., `2.3`), that overrides auto-increment.

- **Top-level directory detection**:

  - Each changed directory is treated as a separate container image.

# Adding or Updating Docker Images

## Adding a New Docker Image for a New Project

1. Create a **new folder** at the top level of this repository, for example `tuna-2025/`.

2. Put a **Dockerfile** inside that folder.

3. Commit and push your changes (this will trigger the GitHub Actions workflow). 

   - The GitHub Actions workflow will detect the new directory, build a new Docker image, and push it to GHCR.

4. Make the package public (if non-sensitive and intended for public use) so that others can access it without authentication by going to https://github.com/orgs/PacificCommunity/packages and clicking on the package name. 

   - Click on the “Settings” tab and change the visibility to “Public”.

## Updating an Existing Docker Image

1. **Modify** the Dockerfile in one of the existing folders (e.g. `skj-2025/Dockerfile`).

2. Commit and push your changes  (this will trigger the GitHub Actions workflow).   

   - The workflow detects changes in that directory’s Dockerfile and automatically rebuilds and pushes an updated image to GHCR.

# Automatic GitHub Actions Trigger

- **Workflow trigger**:  

  Whenever you push changes (especially Dockerfile changes), GitHub Actions automatically runs the build-and-push workflow. If anything goes wrong in the build or push process, the workflow will **fail**, and you can check the logs in the “Actions” tab for details.

- **Failing workflow**:  

  If the Docker build fails, version detection fails, or pushing to GHCR fails, you will see a **red “X”** in the GitHub Actions run. View the logs to diagnose and fix the issue before retrying.