Is your container a gigabyte, for a hundred-line service? Many container images start from a full operating system. They carry compilers, shells and download caches into production. Your service needs none of that to run. Every deploy stores it, pulls it and starts it, on every machine. That is storage, network traffic and start-up work, again and again. Here is the fix you can use today. Start from a slim base image, like alpine or distroless. GreenCode researchers found that big container images waste energy. The GreenCode Constitution notes these can be ten to a hundred times smaller. Build in stages, and copy only what the service needs to run. Leave test tools and build tools out of the final image. Get this right using GreenCode's Constitution skill for AI agents, and Docker's build guide. A smaller image means less to store, send and start. GreenCode helps tackle this by mapping your running services and the energy each one uses. It shows which services cause the energy use, and which barely run. That was GreenCode Tech Tip number eight. Follow for the next tip, and find more on greencode.ai/tech-tips.