overshard / docker-teamspeak

A nice and easy way to get a TeamSpeak server up and running using docker.

docker-teamspeak

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 it's website.

Building docker-teamspeak

Running this will build you a docker image with the latest version of both docker-teamspeak and TeamSpeak itself.

git clone https://github.com/overshard/docker-teamspeak
cd docker-teamspeak
docker build -t overshard/teamspeak .

Running docker-teamspeak

Running the first time will set your port to a static port of your choice so that you can easily map a proxy to. If this is the only thing running on your system you can map the ports to 9987, 10011, 30033 and no proxy is needed. i.e. -p=9987:9987/udp -p=10011:10011 -p=30033:30033 Also be sure your mounted directory on your host machine is already created before running mkdir -p /mnt/teamspeak.

sudo docker run -d=true -p=9987:9987/udp -p=10011:10011 -p=30033:30033 -v=/mnt/teamspeak:/data overshard/teamspeak /start

With Teamspeak v3.1 Teamspeak has changed it's license and license policy, before you can start the server you have to accept the License. This you can do by having a file called .ts3server_license_accepted in the working directory or define the enviroment variable TS3SERVER_LICENSE=accept. For the later add to the docker command the following option:

-e TS3SERVER_LICENSE='accept'

E.g.

sudo docker run -d=true -p=9987:9987/udp -p=10011:10011 -p=30033:30033 -v=/mnt/teamspeak:/data -e TS3SERVER_LICENSE='accept' overshard/teamspeak /start

From now on when you start/stop docker-teamspeak you should use the container id with the following commands. To get your container id, after you initial run type sudo docker ps and it will show up on the left side followed by the image name which is overshard/teamspeak:latest.

sudo docker start <container_id>
sudo docker stop <container_id>

File Permissions

Docker has no way to change file permissions at runtime without being root. Because of that you have to make sure every file you want the container to use (database or previous logs) is owned by uid and gid 1000.
Run chown 1000:1000 <filename(s)> on every file or Run chown -R 1000:1000 /mnt/teamspeak to fix all permissions recursively.

docker-compose

You can use docker-compose to simplify the process of building and running.
If you do not wish to import an existing database or logfiles just run:

sudo docker-compose up

This will build and run the container.
If you want to import existing logs or a database read File Permissions first.

Server Admin Token

You can find the server admin token in /mnt/teamspeak/logs/, search the log files for ServerAdmin privilege key created and use that token on first connect.

Alternatively you can run docker logs <container_id> which will display
the logfile.

Notes on the run command

• -v is the volume you are mounting -v=host_dir:docker_dir
• overshard/teamspeak is simply what I called my docker build of this image
• -d=true allows this to run cleanly as a daemon, remove for debugging
• -p is the port it connects to, -p=host_port:docker_port

Major Contributors

• overshard
• giant3gg

Mumble Server Alternative

Benjamin Denhartog has created an alternative MurMur/Mumble server if you're looking for an alternative to Teamspeak.

docker-teamspeak's Issues

Docker hub?

Would it be possible for you guys to set up a simple autobuild on docker hub for this to make it easier for people to use?

mnt/teamspeak is empty?

Im no Linux guy by any means but after starting the docker image.
i wrote cd .. until i was in the root folder docker@boot2docker:/$ then i used cd mnt/teamspeak
now if i write ls there the directory is empty..
So where do i find the log file with the admin key?

i used the following to start sudo docker run -d=true -p=9987:9987/udp -p=10011:10011 -p=30033:30033 -v=/mnt/teamspeak:/data overshard/teamspeak /start

Also i got a few errors while building:

debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype

do i need to care about those?

sudo docker ps results in

CONTAINER ID        IMAGE                 COMMAND             CREATED             STATUS              PORTS                                                                        NAMES
0d8ba6b1c6a3        overshard/teamspeak   "/start"            14 minutes ago      Up 14 minutes       0.0.0.0:10011->10011/tcp, 0.0.0.0:9987->9987/udp, 0.0.0.0:30033->30033/tcp   sharp_lalande

.tar.bz2 not available anymore

TS3 is now only downloadable via .run file. Could you update the Dockerfile, please?

--> https://www.teamspeak.com/en/downloads#server

Updating to newest Teamspeak Server Version?

see title

connected client IP is the local container IP

This seems like unexpected behavior. From my logs:

2016-02-04 05:55:14.916204|INFO |VirtualServerBase| 1| client connected 'malbin'(id:2) from 172.17.0.1:41840

Emphasis on 172.17.0.1 which is definitely not the remote client's IP. Wondering if I'm missing something silly here.

Run teamspeak as unprivileged user

Hi,

just for the paranoid ones of us:
Although this app is running inside a container, Teamspeak should run as unprivileged user.

https://forums.docker.com/t/root-user-or-non-root-user-inside-container/966/3
https://groups.google.com/forum/#!msg/docker-user/e9RkC4y-21E/JOZF8H-PfYsJ

What do you think?

Can't create/write to directory /data for logs

2017-04-12 21:25:28.595099|ERROR |FileHelp | |CustomFileHelpers::createDirectory _wmkdir /data/logs -1 13
2017-04-12 21:25:28.595232|ERROR |ServerLibPriv | |Failed to create "/data/logs" directory
2017-04-12 21:25:28.595437|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.13.6 (2016-11-08 08:48:33)
ERROR: openFile( file:/data/logs/ts3server_2017-04-12__21_25_28.595267_0.log) failed
2017-04-12 21:25:28.595581|INFO |ServerLibPriv | |SystemInformation: Linux 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 Binary: 64bit
ERROR: openFile( file:/data/logs/ts3server_2017-04-12__21_25_28.595267_0.log) failed
2017-04-12 21:25:28.595765|WARNING |ServerLibPriv | |The system locale is set to "C" this can cause unexpected behavior. We advice you to repair your locale!
ERROR: openFile( file:/data/logs/ts3server_2017-04-12__21_25_28.595267_0.log) failed
ERROR: openFile( file:/data/logs/ts3server_2017-04-12__21_25_28.595267_0.log) failed

Cannot connect to query port

Hi,

I cannot connect to the query port. Is there something wrong with my configuration?

docker-compose.yml:

  teamspeak:
    image: overshard/teamspeak
    volumes:
        - './data/teamspeak/:/data/'
    ports:
        - '9987:9987/udp'
        - '30033:30033'
        - '10011:10011'
        - '41144:41144'
    restart: always

  teamspeakbot:
    image: galexrt/jts3servermod
    volumes:
        - './teamspeakbot/config/:/jts3servermod/config'
    restart: always
    links:
      - teamspeak
    ports:
        - 8087:8087

The server is starting up correctly and I can connect to it via telnet or TS3 client.
But any software using the queryport is giving errors, e.g. the JTS3Servermod bot (as in docker-compose file) or a simple TS3 web-viewer.

Empty directory?

Hello guys, I am actually using a similiar docker-compose.yml like in this project but I always have a empty directory in the selected volume.

The server is running fine!

Can you help me maybe?