A nice and easy way to get a TeamSpeak server up and running using docker. For
help on getting started with docker see the official getting started guide.
For more information on TeamSpeak and check out its website.
Running this will build you the latest docker-teamspeak image:
git clone https://github.com/xanderxaj/docker-teamspeak cd docker-teamspeak ./ts3-build.sh
If nothing else is running on ports 9987, 10011 or 30033, launching TeamSpeak is a
simple case of running:
Note: If you get an error about being unable to gain access to docker, you may
need to add yourself to the
docker group or prepend
sudo to the
If the ports are in use, you can remap them by changing the ports in the teamspeak
docker run command. Look for
You can start and stop TeamSpeak by running:
docker start teamspeak docker stop teamspeak
The TeamSpeak container will automatically launch on docker daemon startup or relaunch on
failure unless it has been stopped; this is via docker's
--restart unless-stopped option.
Restricted resource usage
The TeamSpeak container is limited to 100m of RAM and, where supported, 100m of swap. Light testing
suggests this is good enough for most personal TS servers (i.e. with less than 20 users). This can
be adjusted by modifying the
--memory option in
You may get a warning relating to limits on startup, for example:
WARNING: Your kernel does not support swap limit capabilities, memory limited without swap.
This particular message means that RAM usage has been limited but swap has not.
To remove the warnings and enforce the limits, follow the instructions in the Docker
docs to enable support in your kernel.
Managing TeamSpeak's data
The TeamSpeak server's data is stored in a named volume called
A backup with the current date and time can be created by running:
That backup can be restored with:
All data can be erased by deleting the
teamspeak named volume; it'll be recreated when you next execute
docker volume rm teamspeak
Server Admin Token
You can find the server admin token by running
docker logs teamspeak upon first run of the server.
Search for "ServerAdmin privilege key created" and use that token on first connect.
Notes on the run command
-vis the volume you are mounting
teamspeakis the name of the image built by
-dallows this to run cleanly as a daemon, remove for debugging
-pis the port it connects to,
Mumble Server Alternative
Benjamin Denhartog has created an alternative MurMur/Mumble server if you're looking for an alternative to Teamspeak.