Public | Automated Build

Last pushed: 9 days ago
Short Description
TeamSpeak 3 SinusBot by Michael Friese in a Docker image.
Full Description

docker-sinusbot

Image available from:

Docker Image with Sinusbot by Michael Friese.
TeamSpeak 3 SinusBot Homepage: https://sinusbot.com/.

Current version:

Sinusbot: latest beta (>=0.9.16-10f0fad)
TeamSpeak: 3.0.19.4 (this version is required for Sinusbot)

Summary

  • Debian Jessie with the latest version of Sinusbot
  • You can inject your data into the container
    • /data

Usage

Updating the image

Run the below command, to update the image to the latest version:

docker pull quay.io/galexrt/sinusbot:latest

Permissions

The default UID of the user which is used in the container is 3000.
So if you mount a directory from your host you have to set the permission to the user with the UID of 3000.

useradd -u 3000 sinusbot
mkdir -p /opt/docker/sinusbot/data /opt/docker/sinusbot/scripts
chown -R sinusbot:sinusbot /opt/docker/sinusbot/data /opt/docker/sinusbot/scripts

Or if you dont want to create an user just use

mkdir -p /opt/docker/sinusbot/data /opt/docker/sinusbot/scripts
chown -R 3000:3000 /opt/docker/sinusbot

Or just use the built-in variables to the run command to change the user and/or group id to an existing or non existing user:
The variables need to be an user/group id not the username:

SINUS_USER=3000
SINUS_GROUP=3000

Mount host directory

docker run \
    --name sinusbot \
    -d \
    -v /opt/docker/sinusbot/data:/sinusbot/data \
    -v /opt/docker/sinusbot/scripts:/sinusbot/scripts \
    -p 8087:8087 \
    galexrt/sinusbot:latest

SELinux

If your host uses SELinux it may be necessary to use the :z option:

docker run \
    --name sinusbot \
    -d \
    -v /opt/docker/sinusbot/data:/sinusbot/data:z \
    -v /opt/docker/sinusbot/scripts:/sinusbot/scripts:z \
    -p 8087:8087 \
    galexrt/sinusbot:latest

Getting Sinusbot image

Normal

Replace CONTAINER_NAME with the container name or ID of the Sinusbot container and check the output for the password of Sinusbot (The password will only be shown on the first run of Sinusbot).

docker logs CONTAINER_NAME

With LOGPATH set

Replace CONTAINER_NAME with the container name or ID and LOGPATH with set value, in the following command:

docker exec CONTAINER_NAME cat LOGPATH

Extra info

  • Shell access while the container is running: docker exec -it sinusbot /bin/bash
  • To monitor the logs in realtime or if you need to grab your sinusbot password: docker logs -f sinusbot
  • Upgrade Youtube-dl to the latest version: docker restart sinusbot or via shell access youtube-dl -U (Normally not needed! A restart of the container updates youtube-dl too)
Docker Pull Command
Owner
galexrt
Source Repository

Comments (5)
lpe672
7 months ago

Hello, I am getting the following error when attempting to connect the bot to a channel. I have been though a lot of troubleshooting and have not found the solution yet...


2017/01/23 13:09:56 38ae95be 2df646dd ERROR TS3Client reported missing dependencies for xcb. Please install xcb and try again. On Ubuntu / Debian you can usually as root run: apt-get install xcb
jerryoman
7 months ago

Is there any fix?
root@Debian:~# docker start sinusbot -i
ln: failed to create symbolic link '/sinusbot/scripts/scripts': File exists
Correcting file and mount point permissions ...
Starting TeamSpeak SinusBot ...

progmem
7 months ago

Same @tharmar

mpk1
8 months ago

Hello,
I have exactly the same problem like @tharmar.
Does somebody know how to fix it?

tharmar
9 months ago

Hello,
my sinusbot won't start. docker logs prints the following:
docker@NUC:~$ docker logs sinusbotTharmar
Correcting file and mount point permissions ...
Starting TeamSpeak SinusBot ...
Correcting file and mount point permissions ...
Starting TeamSpeak SinusBot ...
ln: failed to create symbolic link '/sinusbot/scripts/scripts': File exists

I created the container with this commandline:
docker@NUC:~$ docker run --name sinusbotTharmar -d -v /data/sinusbots/tharmar:/sinusbot/data -p 8087:8087 galexrt/sinusbot:latest

I added the user with the id 3000 before hande and changed the ownership of /data/sinusbots to user sinusbot.

Did I do something wrong? Or where is the error coming from ?