Mirror-Tools
/
shaka-packager
mirror of https://github.com/shaka-project/shaka-packager.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
shaka-packager/packager/testing/dockers/CentOS_Dockerfile

17 lines
483 B
Plaintext
Raw Normal View History

test: Move CentOS 8 tests to CentOS 9 Stream (#1240) CentOS 8 is EOL, and the official docker images will not be updated. See https://www.centos.org/centos-linux-eol/ This switches to the latest release (CentOS 9 Stream). Since CentOS no longer provides official images, this uses a third-party image provider (https://hub.docker.com/u/tgagor) This change also exposed a warning in absl that needed to be silenced in the default version of GCC in CentOS 9 Stream (GCC 11.4).
2023-07-17 18:10:28 +00:00
FROM tgagor/centos:stream9
fix: Roll back depot_tools, bypass vpython (#1045) Using the latest depot_tools no longer works. depot_tools also wants to auto-update itself, which must now be disabled. We also need to disable the copy of python (vpython) included in depot_tools, since for some distros, it has dependencies on system libraries that no longer exist. Finally, we need to force some distros to use python 2, because our build system is ancient and needs to be ripped out and replaced some day soon. This fixes build issues in our CI, our Dockerfiles, and in general on certain platforms or distros. Closes #1023
2022-03-09 00:46:18 +00:00
ci: Enable parallel builds (#1241) Our workflows and Dockerfiles now use Ninja on Linux & Mac, which enables safe parallel builds. This significantly speeds up our workflows. GitHub Actions typical compilation times (build step only): - Linux 19m => 9m - macOS 23m => 8m - Windows 12m => 10m - Linux arm64 (self-hosted) 72m => 29m - Docker build 25m => 14m Overall workflow time: 84m => 33m Compilation time on my workstation (12 CPUs @3.3GHz): 15m => 3m This also adds a new environment variable "PACKAGER_LOW_MEMORY_BUILD". If defined when CMake is first run, this will configure the build to disable parallel linking to reduce memory usage. This helps us avoid failures on our self-hosted arm64 machines, where 6 CPUs share 4GB of RAM. NOTE: Parallel builds are **NOT** recommended with Unix Makefiles due to the use of excessive RAM during parallel linking. Unix Makefiles, unlike Ninja, cannot be configured to restrict parallel linking during a parallel build. Anecdotally, parallel builds with Makefiles have exhausted a system with 32GB RAM. (My workstation.) In a follow-up, I will update the build documentation to refer to CMake and recommend all of the flags now used in our workflows.
2023-07-17 20:16:03 +00:00
# For CentOS, Ninja is only available from the "CRB" ("Code Ready Builder")
# repo. Enable that first.
feat: port HLS module to CMake (#1238) related to issue #1047
2023-08-22 01:41:18 +00:00
RUN dnf update -y
ci: Enable parallel builds (#1241) Our workflows and Dockerfiles now use Ninja on Linux & Mac, which enables safe parallel builds. This significantly speeds up our workflows. GitHub Actions typical compilation times (build step only): - Linux 19m => 9m - macOS 23m => 8m - Windows 12m => 10m - Linux arm64 (self-hosted) 72m => 29m - Docker build 25m => 14m Overall workflow time: 84m => 33m Compilation time on my workstation (12 CPUs @3.3GHz): 15m => 3m This also adds a new environment variable "PACKAGER_LOW_MEMORY_BUILD". If defined when CMake is first run, this will configure the build to disable parallel linking to reduce memory usage. This helps us avoid failures on our self-hosted arm64 machines, where 6 CPUs share 4GB of RAM. NOTE: Parallel builds are **NOT** recommended with Unix Makefiles due to the use of excessive RAM during parallel linking. Unix Makefiles, unlike Ninja, cannot be configured to restrict parallel linking during a parallel build. Anecdotally, parallel builds with Makefiles have exhausted a system with 32GB RAM. (My workstation.) In a follow-up, I will update the build documentation to refer to CMake and recommend all of the flags now used in our workflows.
2023-07-17 20:16:03 +00:00
RUN dnf install -y yum-utils
RUN dnf config-manager --set-enabled crb
test: Update Dockerfiles This updates the main Dockerfile and all the docker-based distro-specific tests. The base OS versions have been updated to versions that have not reached end-of-life status yet, and the list of dependencies required has been updated and pruned. Change-Id: Ibcff2f60e739fd5d999af100af76c40aa91a75bc
2021-10-13 18:00:37 +00:00
# Install utilities, libraries, and dev tools.
RUN yum install -y \
which \
fix: Fix crash in static-linked linux builds The official, static-linked linux builds were crashing in their use of getaddrinfo, which libcurl was configured to use. Both getaddrinfo and all of its alternatives available in glibc fail with static linking. We can fix this by configuring libcurl to use libc-ares on Linux instead. This allows us to keep the benefits of a statically-linked Linux binary. Closes #996 Change-Id: Ib4a9eb939813fd165727788726459ef4adf3fc4d
2021-10-12 21:55:13 +00:00
c-ares-devel libatomic \
ci: Enable parallel builds (#1241) Our workflows and Dockerfiles now use Ninja on Linux & Mac, which enables safe parallel builds. This significantly speeds up our workflows. GitHub Actions typical compilation times (build step only): - Linux 19m => 9m - macOS 23m => 8m - Windows 12m => 10m - Linux arm64 (self-hosted) 72m => 29m - Docker build 25m => 14m Overall workflow time: 84m => 33m Compilation time on my workstation (12 CPUs @3.3GHz): 15m => 3m This also adds a new environment variable "PACKAGER_LOW_MEMORY_BUILD". If defined when CMake is first run, this will configure the build to disable parallel linking to reduce memory usage. This helps us avoid failures on our self-hosted arm64 machines, where 6 CPUs share 4GB of RAM. NOTE: Parallel builds are **NOT** recommended with Unix Makefiles due to the use of excessive RAM during parallel linking. Unix Makefiles, unlike Ninja, cannot be configured to restrict parallel linking during a parallel build. Anecdotally, parallel builds with Makefiles have exhausted a system with 32GB RAM. (My workstation.) In a follow-up, I will update the build documentation to refer to CMake and recommend all of the flags now used in our workflows.
2023-07-17 20:16:03 +00:00
cmake gcc-c++ git ninja-build python3
fix: Roll back depot_tools, bypass vpython (#1045) Using the latest depot_tools no longer works. depot_tools also wants to auto-update itself, which must now be disabled. We also need to disable the copy of python (vpython) included in depot_tools, since for some distros, it has dependencies on system libraries that no longer exist. Finally, we need to force some distros to use python 2, because our build system is ancient and needs to be ripped out and replaced some day soon. This fixes build issues in our CI, our Dockerfiles, and in general on certain platforms or distros. Closes #1023
2022-03-09 00:46:18 +00:00
Add docker files for testing on various linux distros Change-Id: Ic05e2dc326a2b70c43132118d78f6d496d8b7e18
2017-12-07 22:41:14 +00:00
# Build and run this docker by mapping shaka-packager with
# -v "shaka-packager:/shaka-packager".