Source: https://gameye.com/glossary/containers/

---
title: "Containers | Gameye"
description: "A container is a packaged, portable software unit. For game servers, it’s your entire server build — easy to deploy, replicate, and roll back."
---

# Containers

A container is a packaged set of data or software. But for your case, it’ll be a packaged version of your entire game, or any updates you need to send out. ‘Containerizing’ makes it easier and faster to roll out into production on the game servers (and to also quickly roll back any previous versions you may have out there).

What’s great about using containers is you can quickly deploy, replicate, move, and back up your game servers.

## Containers reduce queue times

If a server crashes, of you have a spike of players in a location where you’re not setup, then having containers of your game will make it quicker and easier to fire up new game servers.

**See also:** [Gameye vs. Agones — why managed container orchestration beats self-hosted Kubernetes](https://gameye.com/gameye-vs-agones/) · [How Gameye orchestration works](https://gameye.com/how-it-works/)

Building a multiplayer game? Gameye hosts dedicated game servers: ship your server as a Docker container and start one per match with a single API call, in a region near your players.

[See how it works →](https://gameye.com/how-it-works/)

[Back to Glossary](https://gameye.com/glossary/)

## Related terms

- ### Data packet

A data packet is game data — position, inputs, events — sent across the network. Packet size and send rate directly affect latency and bandwidth use. [Read more](https://gameye.com/glossary/data-packet/)
- ### Resource profile

A resource profile will figure out how many resources your game will take, and in turn, how much compute power a server needs to reserve to run your game. [Read more](https://gameye.com/glossary/resource-profile/)