edgegap-containerize
Package any game server (Unreal, Godot, Node, Go, Rust, C++, a Unity build) into a Docker image that runs correctly on Edgegap, push it to the Edgegap Container Registry or Docker Hub, GHCR, ECR, GCR or GitLab, and register it as an app version: the container contract, Dockerfile patterns, linux/amd64 builds on Apple Silicon, image tags, registry credentials on the version, and port mapping. Use whenever writing or fixing a Dockerfile for a game server, building on a Mac, pushing to registry.edgegap.com, getting "unable to pull image" or exec format errors, or when someone asks how to get a server build onto Edgegap. Engine-agnostic; edgegap-unity has a ready Unity Dockerfile.
Target: Design & content creation. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Containerizing a game server for Edgegap
- The container contract
- Dockerfile pattern
- Build and push
- Register it as an app version
- Verify before shipping
An image runs correctly on Edgegap when: 1. It is linux/amd64. Edgegap runs Linux x86-64 only. No Windows containers, no ARM images. On Apple Silicon and other ARM machines, always build with --platform linux/amd64; an ARM image fails on Edgegap with exec format error or "not found". 2. The server starts with no input. No prompts, no TTY, headless flags on (Unity -batchmode -nographics, Godot --headless, Unreal server target with -log). Configuration arrives as env vars (edgegap-server-design). 3. The game server is PID 1, or receives signals. Use exec-form CMD/ENTRYPOINT (["./server", "-log"]), or end a start script with exec ./server "$@". A shell that stays PID 1 swallows SIGTERM and the server dies at SIGKILL without draining. npm start has the same problem; run node server.js directly. 4. It binds 0.0.0.0 on the internal port declared in the app version, with the matching protocol. 5. It logs to stdout/stderr. Log files inside the container are invisible to Edgegap. 6. No secrets in the image. Not the Edgegap API token, not registry credentials, not third-party keys. Secrets go on the app version as hidden env vars. 7. It never prints its environment. env; in a CMD (common in
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- edgegap/llm-agent-skills
- Source file
- skills/edgegap-containerize/SKILL.md
- Fixed revision
- fd510ba826ea29ab359e70e185d2e650ef6827de
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: edgegap/llm-agent-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T08:01:42.839Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.