linuxserver/minisatip¶
Minisatip is a multi-threaded satip server version 1.2 that runs under Linux and it was tested with DVB-S, DVB-S2, DVB-T, DVB-T2, DVB-C, DVB-C2, ATSC and ISDB-T cards.
Supported Architectures¶
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/minisatip:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture | Available | Tag |
---|---|---|
x86-64 | ✅ | amd64-<version tag> |
arm64 | ✅ | arm64v8-<version tag> |
armhf | ❌ |
Application Setup¶
Best used in conjunction with tvheadend
There is no setup per se, other than adding your cards for passthrough.
You can then use your cards as DVB inputs in apps such as tvheadend.
Usage¶
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
Info
Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.
docker-compose (recommended, click here for more info)¶
---
services:
minisatip:
image: lscr.io/linuxserver/minisatip:latest
container_name: minisatip
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- RUN_OPTS=
volumes:
- /path/to/minisatip/config:/config
ports:
- 8875:8875
- 554:554
- 1900:1900/udp
devices:
- /dev/dvb:/dev/dvb
restart: unless-stopped
docker cli (click here for more info)¶
docker run -d \
--name=minisatip \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-e RUN_OPTS= \
-p 8875:8875 \
-p 554:554 \
-p 1900:1900/udp \
-v /path/to/minisatip/config:/config \
--device /dev/dvb:/dev/dvb \
--restart unless-stopped \
lscr.io/linuxserver/minisatip:latest
Additional runtime parameters¶
In some cases it might be necessary to start minisatip with additional parameters, for example to configure a unicable LNB. Add the parameters you need and restart the container. Be sure to have the right parameters set as adding the wrong once might lead to the container not starting correctly. For a list of minisatip parameters visit Minisatip page.
Parameters¶
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal>
respectively. For example, -p 8080:80
would expose port 80
from inside the container to be accessible from the host's IP on port 8080
outside the container.
Ports (-p
)¶
Parameter | Function |
---|---|
8875:8875 | Status Page WebUI |
554:554 | RTSP Port |
1900:1900/udp | App Discovery |
Environment Variables (-e
)¶
Env | Function |
---|---|
PUID=1000 | for UserID - see below for explanation |
PGID=1000 | for GroupID - see below for explanation |
TZ=Etc/UTC | specify a timezone to use, see this list. |
RUN_OPTS= | Specify specific run params for minisatip |
Volume Mappings (-v
)¶
Volume | Function |
---|---|
/config | Configuration files and minisatip data |
Device Mappings (--device
)¶
Parameter | Function |
---|---|
/dev/dvb | For passing through Tv-cards |
Miscellaneous Options¶
Parameter | Function |
---|---|
Environment variables from files (Docker secrets)¶
You can set any environment variable from a file by using a special prepend FILE__
.
As an example:
Will set the environment variable MYVAR
based on the contents of the /run/secrets/mysecretvariable
file.
Umask for running applications¶
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022
setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
User / Group Identifiers¶
When using volumes (-v
flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID
and group PGID
.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000
and PGID=1000
, to find yours use id your_user
as below:
Example output:
Docker Mods¶
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Support Info¶
-
Shell access whilst the container is running:
-
To monitor the logs of the container in realtime:
-
Container version number:
-
Image version number:
Updating Info¶
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Via Docker Compose¶
-
Update images:
-
All images:
-
Single image:
-
-
Update containers:
-
All containers:
-
Single container:
-
-
You can also remove the old dangling images:
Via Docker Run¶
-
Update the image:
-
Stop the running container:
-
Delete the container:
-
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/config
folder and settings will be preserved) -
You can also remove the old dangling images:
Image Update Notifications - Diun (Docker Image Update Notifier)¶
Tip
We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
Building locally¶
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-minisatip.git
cd docker-minisatip
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/minisatip:latest .
The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64
.
Versions¶
- 30.06.24: - Rebase to Alpine 3.20.
- 08.12.23: - Rebase to Alpine 3.19, switch to building from releases rather than commits.
- 26.07.23: - Build with DDCI=1 for Digital Devices CI support.
- 03.07.23: - Deprecate armhf. As announced here
- 12.11.22: - Rebasing to alpine 3.137, upgrading to s6v3.
- 23.01.21: - Rebasing to alpine 3.13.
- 01.06.20: - Rebasing to alpine 3.12.
- 19.12.19: - Rebasing to alpine 3.11.
- 28.06.19: - Rebasing to alpine 3.10.
- 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
- 22.02.19: - Rebasing to alpine 3.9.
- 20.02.19: - Fix run options.
- 11.02.19: - Add pipeline logic and multi arch.
- 28.08.18: - Rebase to Alpine 3.8.
- 13.12.17: - Rebase to Alpine 3.7.
- 28.05.17: - Rebase to Alpine 3.6.
- 08.02.17: - Rebase to Alpine 3.5 and only compile libs in dvb-apps.
- 14.10.16: - Add version layer information.
- 18.09.16: - Add support for Common Interface.
- 11.09.16: - Add layer badges to README.
- 28.08.16: - Add badges to README.
- 15.08.16: - Initial Release.