OCI image builder
  • Python 89.6%
  • Shell 10.4%
Find a file
2026-05-13 17:07:29 +03:00
.ash .ash added for testing 2026-04-16 19:59:32 +03:00
.forgejo/workflows workflow updated: ALTFLOW_URL moved to vars 2026-05-12 11:28:40 +03:00
core feat: render Dockerfiles from image metadata packages 2026-05-13 17:07:29 +03:00
org feat: render Dockerfiles from image metadata packages 2026-05-13 17:07:29 +03:00
tests feat: render Dockerfiles from image metadata packages 2026-05-13 17:07:29 +03:00
.gitignore first implementation 2026-04-17 02:01:45 +03:00
config.py Prepare for 'base' image supportion 2026-05-12 14:18:49 +03:00
flowforge.py Modern nameing convention 2026-05-12 15:34:57 +03:00
LICENSE Initial commit 2026-04-16 19:54:42 +03:00
README.md Prepare for 'base' image supportion 2026-05-12 14:18:49 +03:00

flowforge

OCI image builder that uses ALTFlow as backend.

Project heavily inspired by cloud/image-forge

Warning

This repo is WIP. Now tested suppotion for alt organization. base organization probably do not work cause existing of "distroless"

TODO

  • Multi architecture build support
  • Image versions tags
  • Optimize RDB API callings amount
  • base image supportion
  • k8s image supportion
  • distroless image supportion

Requirements

  • python3-module-aiohttp
  • python3-module-pydantic
  • python3-module-pydantic-settings
  • python3-module-loguru
  • python3-module-tomli
  • python3-module-jinja2
  • python3-module-yaml

How to do X?

There are several arguments that passes by environment, here is a list:

  • DRY
  • ALTFLOW_URL
  • ALTFLOW_AUTH
  • REGISTRY_URL (in future)
  • REGISTRY_AUTH
  • SOURCE_REGISTRY (in future)
  • SOT_REPO (in future)

As long as that project will be WIP. REGISTRY_URL & SOURCE_REGISTRY is baked in code.

How to build image

./flowforge.py -i alt/nginx`

How to build organization

./flowforge.py -o alt