containerfile-standards

Automate standard Containerfile patterns for BC Gov .NET API and React/Vite projects.

7|Updated Mar 5, 2026

Search Tags:#security #dockerfile #openshift #healthcheck #runtime-config #containerfile #bc-gov

Ready to run

npx skills add https://github.com/rloisell/rl-agents-n-skills --skill containerfile-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: containerfile-standards
Source: https://github.com/rloisell/rl-agents-n-skills/tree/main/containerfile-standards
Command: npx skills add https://github.com/rloisell/rl-agents-n-skills --skill containerfile-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Containerfile patterns for BC Gov projects to ensure consistent security, port usage, and runtime behavior across .NET API and React/Vite frontend images.

Core Features & Use Cases

Enforces port 8080 exposure inside all container images.
Requires a non-root appuser and includes HEALTHCHECK guidance.
Provides a consistent runtime configuration approach for frontend API URLs using a config.json pattern.
Use Case: When creating or updating any Containerfile or Dockerfile for BC Gov deployments, apply these standards to reduce drift and deployment issues.

Quick Start

Follow these guidelines when creating or updating any Containerfile or Dockerfile for BC Gov projects.

Frequently Asked Questions about containerfile-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a standard Containerfile for BC Gov OpenShift deployments?▼

To create a standard Containerfile for BC Gov, apply patterns enforcing port 8080 exposure, a non-root appuser, HEALTHCHECK instructions, and a runtime config.json approach for React/Vite API URLs.

What security hardening patterns are required for BC Gov container images?▼

Security hardening for BC Gov container images requires specifying a non-root appuser, including HEALTHCHECK guidance, and enforcing port 8080 exposure to ensure consistent runtime behavior in OpenShift.

How do I configure runtime API URLs for a React/Vite frontend in a container?▼

Configure runtime API URLs for React/Vite frontends by implementing a config.json pattern in your Containerfile, allowing dynamic configuration updates without rebuilding the container image.

Do I need to expose port 8080 for .NET API container images in OpenShift?▼

Yes, exposing port 8080 is a mandatory standard for all BC Gov container images, including .NET API and React/Vite frontends, ensuring consistent network routing in OpenShift deployments.

Does this Containerfile standard work with both .NET API and React/Vite projects?▼

Yes, these Containerfile standards apply to both .NET API and React/Vite frontend projects, enforcing mandatory checks for port 8080, non-root users, health checks, and runtime configuration patterns.

Why does my BC Gov container deployment fail runtime configuration checks?▼

Runtime configuration checks fail when Containerfiles lack the required config.json pattern for frontend API URLs, miss port 8080 exposure, or do not define a non-root appuser for OpenShift deployments.