| Age | Commit message (Collapse) | Author |
|
* Fix Vaapi Intel packages
https://github.com/jellyfin/jellyfin/issues/1901#issuecomment-593114951
Still need to compile with the packages to verify it builds properly. Arm builds probably need it too.
* Update Dockerfile
* Update Dockerfile
* Update Dockerfile.arm
* Update Dockerfile.arm
* Update Dockerfile.arm64
* Update Dockerfile.arm
* Update Dockerfile.arm
* Update Dockerfile.arm
* Update Dockerfile.arm64
* Update Dockerfile.arm64
* Update Dockerfile.arm
* Update Dockerfile
* shift from curl to git for web install
removed the necessity of curl, tar and package availability and using the source directly
* Update Dockerfile.arm
* Update Dockerfile.arm64
* Update Dockerfile
* Update Dockerfile
* Update Dockerfile.arm
* Update Dockerfile.arm64
* clean up packages and remove unnecessary ARG
* Update Dockerfile
* Update Dockerfile.arm64
* Update Dockerfile
* Update Dockerfile.arm64
* Update Dockerfile
* Update Dockerfile.arm
* Update Dockerfile.arm64
* Explainations
* Update Dockerfile.arm
* Update Dockerfile.arm64
|
|
https://github.com/jellyfin/jellyfin-web/pull/735
I had to install git to get it to build ✌️
|
|
|
|
|
|
|
|
use exec form for Dockerfile entrypoint
|
|
Depending on configuration the docker container may need OpenSSL to support https access
|
|
debian-stretch packages were missing for libva-drm2 so would not build
the base image mcr.microsoft.com/dotnet/core/sdk:${DOTNET_VERSION} is incorrectly referencing .NET Core 3-preview6 which will cause issues at runtime with library references being mismatched
|
|
This causes the jellyfin process to be pid 1 in the container. It can
receive signals like SIGTERM (from "docker stop", for example) and shut
down properly.
|
|
The self contained packages already contains the dotnet runtime
No need to use the dotnet runtime base image.
This should decrease the size of the image.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The common.build.sh script was removed in #1793 but the Dockerfiles
still used this to perform the dotnet publish. Remove that call and do
the publish explicitly.
|
|
|
|
|
|
|
|
Bump version to 10.4.0
|
|
|
|
|
|
|
|
|
|
This allows for building against jellyfin-web master. Ex.
docker build . --build-arg JELLYFIN_WEB_VERSION=master
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Use new dotnet image paths
* Update jellyfin-web to 10.3.0-rc1
|
|
|
|
Removed --ffprobe from src files and server/docker scripts.
|
|
|
|
Will always ensure containers use correct path.
Yes - the arm images have a different path than the amd64 one. This is
caused by the amd64 image using ffmpeg from jellyfin/ffmpeg while the
others use ffmpeg from their distro's repos.
|
|
Signed-off-by: Thomas Büttner <thomas@vergesslicher.tech>
|
|
Signed-off-by: Thomas Büttner <thomas@vergesslicher.tech>
|
|
|
|
Adds the /cache volume and set it to writeable by all. This allows for
those using jellyfin to continue using it without modifying their
config. However, retaining cache will require one to mount the /cache
volume.
Also make the /config and /media dirs 777 by default. No permissions on
mounted volumes will be changed.
|
|
* Prevent failure when obj exists from host compile
* Enhance readability of disposed stages
* Formatting
|
|
|
|
After the change to runtime args in #749 docker broke.
This fixes it.
|
|
Eventually would like to move to his 4.0-vaapi image
|
|
By moving the apt-get layer before the copies, the apt-get layer can be reused with each build, reducing upload/download needed during updates.
Just a small optimization.
|
|
#606 didn't actually run the new commands due to the comments position.
This fixes the comment location.
|