edgegap-containerize

原文涵盖的主题

• 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

这里只展示节选，请以完整原文和当前要求为准。