linuxserver.io

Community Developer
  • Posts

    202
  • Joined

  • Days Won

    7

Everything posted by linuxserver.io

  1. Application Name: Oscam Application Site: http://www.streamboard.tv/oscam/ Docker Hub: https://hub.docker.com/r/linuxserver/oscam/ Github: https://github.com/linuxserver/docker-oscam Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
  2. It appears that a lack of support for ipv6 in unRAID is currently preventing teamspeak3 server from starting. We are currently investigating a method to force ipv4 but until further notice this Container is not working.
  3. Thank you very much for your donation. Helps to keep us up and running.
  4. This docker has been rebased to alpine linux with s6 overlay, please make sure you backup your appdata first before you update to this latest image. As part of our repository restructuing, it has also been moved from lsiodev to main linuxserver repository. https://hub.docker.com/r/linuxserver/daapd/ linuxserver/daapd please update your templates accordingly. For more information, please read : http://lime-technology.com/forum/index.php?topic=50793.0
  5. This docker has been rebased to ubuntu xenial with s6 overlay, please make sure you backup your appdata first before you update to this latest image. As part of our repository restructuing, it has also been moved from lsiodev to main linuxserver repository. https://hub.docker.com/r/linuxserver/plexrequests/ linuxserver/plexrequests please update your templates accordingly. For more information, please read : http://lime-technology.com/forum/index.php?topic=50793.0
  6. Application Name: TVHeadend Application Site: https://tvheadend.org/ Docker Hub: https://hub.docker.com/r/linuxserver/tvheadend/ Github: https://github.com/linuxserver/docker-tvheadend Please post any questions/issues relating to this docker you have in this thread. **Notes** - Please take a look at the readme's about how the tags work for this docker image. Migration from tobben's TVHeadend docker should work fine but you may need to reconfigure xmltv If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
  7. This docker has been rebased to alpine/xenial (dependant on branch) with s6 overlay, please make sure you backup your appdata first before you update to this latest image. The following branches are available (see first post for more information) Helix Isengard Jarvis Krypton - at time of post , is in beta. For more information, please read : http://lime-technology.com/forum/index.php?topic=50793.0
  8. +1 And here is the link for the DVR version on plex forum: Using the special DVR Beta "rest assured this will be available as an automatic update for Plex Pass users before long"
  9. Application Name: The-Lounge Application Site: https://thelounge.github.io/ Docker Hub: https://hub.docker.com/r/linuxserver/thelounge/ Github: https://github.com/linuxserver/docker-thelounge Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
  10. This docker has been rebased to alpine with s6 overlay, additionally it has been moved to our community repository, please make sure you backup your appdata first before you update to this latest image. For more information, please read : http://lime-technology.com/forum/index.php?topic=50793.0
  11. Container has been moved into our main repository, please update your templates accordingly. linuxserver/musicbrainz hub url: https://hub.docker.com/r/linuxserver/musicbrainz/
  12. This docker has been rebased to alpine with s6 overlay, please make sure you backup your appdata first before you update to this latest image. Also the image has been moved from our lsiodev repository to our main linuxserver repository. For more information, please read : http://lime-technology.com/forum/index.php?topic=50793.0
  13. Image has been moved from beta to a full release, please update to the new release image as the beta repository has now been deleted.
  14. Application Name: COPS (Calibre OPDS PHP Server) Application Site: https://github.com/seblucas/cops Docker: https://hub.docker.com/r/linuxserver/cops/ Github: https://github.com/linuxserver/docker-cops/ Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support
  15. Over the past couple of months, there have been a few things going on in the Linuxserver.io world which has led to a slower pace of development and a little less community interaction, and for that we can only apologise. Now we are starting to get back in full swing, we thought we should share what we’ve got planned in the next few weeks & months. REPOSITORIES First of all, there will be some restructuring with our fleet of dockers. Some of our dockers are becoming increasingly difficult to support, so we have decided to re-organise the repo’s. linuxserver Our current main docker repository which will have the fleet of dockers that the team actively supports. linuxserver-community This will be a new, innovative repo, that is for any docker requests from community members that we produce and are not used by any of the linuxserver.io team and will therefore be directly supported by community members themselves. All of the linuxserver.io members are volunteers and do this in our spare time, which is finite. The idea behind this is that if you request a docker and we produce it, then YOU become responsible for helping support it, as you are better placed to do so as an active user. You will become the community liason and named as such. We’d like to see you help other members with any problems and liase with us about any problems you can’t fix or need help with via the forum, github or IRC and work with us to keep this maintained. No coding ability is required, just a willingness to “muck in” and monitor the support thread for the container. If you don’t do so, and “request and run” AND nobody else offers to take over, then eventually we’ll pull the container as it’s not fair to other users if we can’t offer support. lsioarmhf Our second new repo, this time it will be for all you users that want to run our dockers on any armhf platform capable of running the docker service, such as your raspberry pi’s / Odroid boxes. These dockers will be duplicates of the images we create for x86 and will also be both linuxserver and linuxserver-community varieties, lsiodev Our development repo and not for production use. Note, up to now, some of our “non-standard” containers have been in this repo but these will be merged into our main repo going forward and this repo will purely be for development and pre-release testing, therefore unsupported and not recommended for end users. lsiobase Our repo to house all our base images. Over the next couple of weeks, you will therefore find that some Docker containers will be moved to different repo’s or possibly even removed, we don’t yet have a final list of what is being moved/removed yet but if you have any concerns, feel free to get in touch on Github or IRC. BASEIMAGE UPDATES Over the next couple of weeks, we will be switching our containers to a shiny new base image – Alpine. Anything that doesn’t run on Alpine will be rebased to Xenial as we have decided to drop Phusion due to lack of updates and Alpine offers significant advantages in terms of reducing container sizes. We don’t anticipate any major migration issues with the transition from Phusion to Alpine but please please please backup your appdata first before you update our containers. AUTO-UPDATING After much discussion, we have decided that we are going to change our containers regarding the autoupdate feature. Autoupdates have probably been the biggest generator of support issues with our images and as such , in conjunction with the baseimage updates, we are moving towards having the majority of our images not autoupdate, a notable exception being plex media server. Aside from configuration mismatches from version to version and stability issues, the update routines are processor intensive and make containers slow to start. To mitigate this we plan to update the applications more frequently in the future with more regular image refreshes. WEBSITE/FORUM We are planning on doing some maintenance work in regards to the website and forum, a bit of a clean up and try to get some fresh content back into the site. PODCAST Currently the podcast has been put on hold, we have had amazing feedback for this and plan to start this up again soon! COMMUNITY As always we’re a team of volunteers, we rely both on donations and contributions from our own pockets to keep this project going. So as always if you think you can help in any way then please get in touch. Either by helping with support, development, articles for the website or donations. LinuxServer.io Team.
  16. Over the past couple of months, there have been a few things going on in the Linuxserver.io world which has led to a slower pace of development and a little less community interaction, and for that we can only apologise. Now we are starting to get back in full swing, we thought we should share what we’ve got planned in the next few weeks & months. REPOSITORIES First of all, there will be some restructuring with our fleet of dockers. Some of our dockers are becoming increasingly difficult to support, so we have decided to re-organise the repo’s. linuxserver Our current main docker repository which will have the fleet of dockers that the team actively supports. linuxserver-community This will be a new, innovative repo, that is for any docker requests from community members that we produce and are not used by any of the linuxserver.io team and will therefore be directly supported by community members themselves. All of the linuxserver.io members are volunteers and do this in our spare time, which is finite. The idea behind this is that if you request a docker and we produce it, then YOU become responsible for helping support it, as you are better placed to do so as an active user. You will become the community liason and named as such. We’d like to see you help other members with any problems and liase with us about any problems you can’t fix or need help with via the forum, github or IRC and work with us to keep this maintained. No coding ability is required, just a willingness to “muck in” and monitor the support thread for the container. If you don’t do so, and “request and run” AND nobody else offers to take over, then eventually we’ll pull the container as it’s not fair to other users if we can’t offer support. lsioarmhf Our second new repo, this time it will be for all you users that want to run our dockers on any armhf platform capable of running the docker service, such as your raspberry pi’s / Odroid boxes. These dockers will be duplicates of the images we create for x86 and will also be both linuxserver and linuxserver-community varieties, lsiodev Our development repo and not for production use. Note, up to now, some of our “non-standard” containers have been in this repo but these will be merged into our main repo going forward and this repo will purely be for development and pre-release testing, therefore unsupported and not recommended for end users. lsiobase Our repo to house all our base images. Over the next couple of weeks, you will therefore find that some Docker containers will be moved to different repo’s or possibly even removed, we don’t yet have a final list of what is being moved/removed yet but if you have any concerns, feel free to get in touch on Github or IRC. BASEIMAGE UPDATES Over the next couple of weeks, we will be switching our containers to a shiny new base image – Alpine. Anything that doesn’t run on Alpine will be rebased to Xenial as we have decided to drop Phusion due to lack of updates and Alpine offers significant advantages in terms of reducing container sizes. We don’t anticipate any major migration issues with the transition from Phusion to Alpine but please please please backup your appdata first before you update our containers. AUTO-UPDATING After much discussion, we have decided that we are going to change our containers regarding the autoupdate feature. Autoupdates have probably been the biggest generator of support issues with our images and as such , in conjunction with the baseimage updates, we are moving towards having the majority of our images not autoupdate, a notable exception being plex media server. Aside from configuration mismatches from version to version and stability issues, the update routines are processor intensive and make containers slow to start. To mitigate this we plan to update the applications more frequently in the future with more regular image refreshes. WEBSITE/FORUM We are planning on doing some maintenance work in regards to the website and forum, a bit of a clean up and try to get some fresh content back into the site. PODCAST Currently the podcast has been put on hold, we have had amazing feedback for this and plan to start this up again soon! COMMUNITY As always we’re a team of volunteers, we rely both on donations and contributions from our own pockets to keep this project going. So as always if you think you can help in any way then please get in touch. Either by helping with support, development, articles for the website or donations. LinuxServer.io Team.
  17. Application Name: Minisatip Application Site: https://github.com/catalinii/minisatip Docker Hub: https://hub.docker.com/r/linuxserver/minisatip/ Github: https://github.com/linuxserver/docker-minisatip Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
  18. Application Name: Nextcloud Application Site: https://nextcloud.com/ Docker Hub: https://hub.docker.com/r/linuxserver/nextcloud/ Github: https://github.com/linuxserver/docker-nextcloud Note: Requires MariaDB or MySQL, please note the issues with binlogging detailed here. This is a Nextcloud issue which we have no control over. https://info.linuxserver.io/issues/2023-06-25-nextcloud/ For setup guide please see the article on our website here. Image is now upgrading Nextcloud internally For upgrading the Nextcloud version there are 3 options. 1. Update via the webui when the upgrade shows as available. 2. Update from the terminal when the upgrade shows as available with: docker exec -it nextcloud updater.phar 3. Manual upgrade using occ. ##Turn on maintenance mode docker exec -it nextcloud occ maintenance:mode --on ##Backup current nextcloud install docker exec -it nextcloud mv /config/www/nextcloud /config/www/nextcloud-backup ##Grab newest nextcloud release and unpack it docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest.tar.bz2 -P /config docker exec -it nextcloud tar -xvf /config/latest.tar.bz2 -C /config/www ##Copy across old config.php from backup docker exec -it nextcloud cp /config/www/nextcloud-backup/config/config.php /config/www/nextcloud/config/config.php ##Now Restart docker container docker restart nextcloud ##Perform upgrade docker exec -it nextcloud occ upgrade ##Turn off maintenance mode docker exec -it nextcloud occ maintenance:mode --off ## Now Restart docker container docker restart nextcloud Once all is confirmed as working: ##Remove backup folder docker exec -it nextcloud rm -rf /config/www/nextcloud-backup ##Remove Nextcloud tar file docker exec -it nextcloud rm /config/latest.tar.bz2 Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
  19. IMPORTANT Anyone that was using the beta container, switch to this container. The beta container has been removed.
  20. As off March 13, 2021 this image has been deprecated, read the notice here https://info.linuxserver.io/issues/2021-03-13-rutorrent/ Application Name: Rutorrent Application Site: https://github.com/Novik/ruTorrent/ Docker Hub: https://hub.docker.com/r/linuxserver/rutorrent/ Github: https://github.com/linuxserver/docker-rutorrent Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support. Rtorrent has a comprehensive list of options and this should be the first port of call for configuration option/issues https://github.com/rakshasa/rtorrent/wiki/rTorrent-0.9-Comprehensive-Command-list-(WIP)#comprehensive-list-of-rtorrent-09-commands **Attention - Latest Update - Image Rewrite** 11/12/2018 We have rewrite to our newest image, so much more lightweight, supports theme folders, fixes a known shutdown bug. Please make sure you backup your appdata before updating in case of any issues. IMPORTANT 23/08/2018 If after updating the image you see message in the webui about rtorrent connection etc, you will need to delete or comment out the following 2 lines in /config/rtorrent/rtorrent.rc. You should comment or delete them regardless if they are set to yes or no. use_udp_trackers = yes peer_exchange = yes restart the container and the problem should be resolved.
  21. Application Name: Muximux Application Site: https://github.com/mescon/Muximux Docker Hub: https://hub.docker.com/r/linuxserver/muximux/ Github: https://github.com/linuxserver/docker-muximux Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
  22. As you might have heard, over at LinuxServer.io we've started a new podcast (https://www.linuxserver.io/index.php/category/podcast/) covering all things Linux, Technology and specifically Docker. Coming up next weeks show we have a special guest from Docker answering your questions. Please submit your question to [email protected] (or below) for a chance to have it answered by Dave Tucker, Product Manager for Open Source at Docker. Dave has a networking background so questions around the network stack might get some good answers... Otherwise anything you wished Docker did, but doesn't. Anything it does do but wished it didn't? Submit it and we'll put it to Dave. Happy Dockering!! IB
  23. Application Name: Plex Requests Application Site: http://plexrequests.8bits.ca/ Docker Hub: https://hub.docker.com/r/linuxserver/plexrequests/ Github: https://github.com/linuxserver/docker-plexrequests Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.