Similarly to the custom scripts, just create a new directory at /custom-services.d. There might also be a need to run an additional service in a container alongside what we already package. #!/bin/bashĪpk add -no-cache ffmpeg Custom Services

Add this bad boy into a script file (can be named anything) and you're good to go. One example use case is our Piwigo container has a plugin that supports video, but requires ffmpeg to be installed. Where possible, to improve security, we recommend mounting them read-only ( :ro) so that container processes cannot write to the location. home/foo/appdata/my-custom-files:/custom-cont-init.d:ro v /home/foo/appdata/my-custom-files:/custom-cont-init.d if using the Docker CLI or services: These scripts can contain logic for installing packages, copying over custom files to other locations, or installing plugins.īecause this location is outside of /config you will need to mount it like any other volume if you wish to make use of it. In every container, simply create a new folder located at /custom-cont-init.d and add any scripts you want. The first part of this update is the support for a user's custom scripts to run at startup.

If you are having an issue with one of our containers, be sure to disable all custom scripts/services/mods before seeking support. NOTE: While the following support has been added to our containers, we will not give support to any custom scripts, services, or mods. This comes in the form of 3 different tools:Īll of the functionality described in this post is live on every one of the containers we currently maintain: Conventionally when people needed some form of custom functionality they would fork our source and build something once that suited their needs leaving this dangling fork without updates or basic maintenance.īehind the scenes we have been working to provide the community with the ability to customize our images not only for themselves but also for other users. Something we provide and pride ourselves on is keeping our containers up to date with not only the latest external software releases, but also with the latest distribution level packages. As it has become very difficult for us to support Swiss Army Knife style images we are looking to the community of users to start customizing our base image layer themselves.

As the projects that we package and distribute grow, conventionally so do the use cases along with large communities of power users. One of the challenges we face as an organization is making everyone happy with the functionality we provide for the software we package in Docker containers.

Universal media server docker