UncleSam
New member
Hi there,
I wanted to use teaspeak server and teaspeak web using docker containers. But all in all I only found outdated versions.
So I decided to create my own docker image which is up2date. But after a look into the official docker github (https://github.com/TeaSpeak/TeaDocker/) I found some good Dockerfiles.
All in all I am now monitoring for new server and web versions (hourly). If there is one an automatically built is triggered and pushed to hub.docker.com - using the original Dockerfiles.
For me I have most up2date versions but if you want feel free to also use them. You can get them here:
How its done:
Inside the original Dockerfiles for server and web are methods to determinate the newest version. With jenkins CI I am now monitoring this path to see if there is a new version (using Plugin URLTrigger, hourly). If there is a change, I am simply fetching the newest TeaDocker github project, build the image using the original Dockerfile and push them to the repositories mentioned above.
Maybe this is interesting for someone
---- Automatically Merged Double Post ----
(sry I think I choosed the wrong cathegory)
I wanted to use teaspeak server and teaspeak web using docker containers. But all in all I only found outdated versions.
So I decided to create my own docker image which is up2date. But after a look into the official docker github (https://github.com/TeaSpeak/TeaDocker/) I found some good Dockerfiles.
All in all I am now monitoring for new server and web versions (hourly). If there is one an automatically built is triggered and pushed to hub.docker.com - using the original Dockerfiles.
For me I have most up2date versions but if you want feel free to also use them. You can get them here:
- Server: https://hub.docker.com/repository/docker/ruepp/teaspeak_server (tags: ubuntu, debian - alpine was not working)
- Web: https://hub.docker.com/repository/docker/ruepp/teaspeak_web (tags: alpine)
How its done:
Inside the original Dockerfiles for server and web are methods to determinate the newest version. With jenkins CI I am now monitoring this path to see if there is a new version (using Plugin URLTrigger, hourly). If there is a change, I am simply fetching the newest TeaDocker github project, build the image using the original Dockerfile and push them to the repositories mentioned above.
Maybe this is interesting for someone
---- Automatically Merged Double Post ----
(sry I think I choosed the wrong cathegory)
Last edited: