2021-10-15 02:41:15 +02:00
|
|
|
# This Dockerfile uses three stages.
|
|
|
|
# 1. Compile anki (and dependencies) and build python wheels.
|
|
|
|
# 2. Create a virtual environment containing anki and its dependencies.
|
|
|
|
# 3. Create a final image that only includes anki's virtual environment and required
|
|
|
|
# system packages.
|
|
|
|
|
|
|
|
ARG PYTHON_VERSION="3.9"
|
|
|
|
ARG DEBIAN_FRONTEND="noninteractive"
|
|
|
|
|
|
|
|
# Build anki.
|
|
|
|
FROM python:$PYTHON_VERSION AS build
|
|
|
|
RUN curl -fsSL https://github.com/bazelbuild/bazelisk/releases/download/v1.7.4/bazelisk-linux-amd64 \
|
|
|
|
> /usr/local/bin/bazel \
|
|
|
|
&& chmod +x /usr/local/bin/bazel \
|
|
|
|
# Bazel expects /usr/bin/python
|
|
|
|
&& ln -s /usr/local/bin/python /usr/bin/python
|
|
|
|
WORKDIR /opt/anki
|
|
|
|
COPY . .
|
|
|
|
# Build python wheels.
|
updates to the build process and binary bundles
All platforms:
- rename scripts/ to tools/: Bazelisk expects to find its wrapper script
(used by the Mac changes below) in tools/. Rather than have a separate
scripts/ and tools/, it's simpler to just move everything into tools/.
- wheel outputs and binary bundles now go into .bazel/out/dist. While
not technically Bazel build products, doing it this way ensures they get
cleaned up when 'bazel clean' is run, and it keeps them out of the source
folder.
- update to the latest Bazel
Windows changes:
- bazel.bat has been removed, and tools\setup-env.bat has been added.
Other scripts like .\run.bat will automatically call it to set up the
environment.
- because Bazel is now on the path, you can 'bazel test ...' from any
folder, instead of having to do \anki\bazel.
- the bat files can handle being called from any working directory,
so things like running "\anki\tools\python" from c:\ will work.
- build installer as part of bundling process
Mac changes:
- `arch -arch x86_64 bazel ...` will now automatically use a different
build root, so that it is cheap to switch back and forth between archs
on a new Mac.
- tools/run-qt* will now automatically use Rosetta
- disable jemalloc in Mac x86 build for now, as it won't build under
Rosetta (perhaps due to its build scripts using $host_cpu instead of
$target_cpu)
- create app bundle as part of bundling process
Linux changes:
- remove arm64 orjson workaround in Linux bundle, as without a
readily-available, relatively distro-agonstic PyQt/Qt build
we can use, the arm64 Linux bundle is of very limited usefulness.
- update Docker files for release build
- include fcitx5 in both the qt5 and qt6 bundles
- create tarballs as part of the bundling process
2022-01-30 01:50:14 +01:00
|
|
|
RUN ./tools/build
|
2021-10-15 02:41:15 +02:00
|
|
|
|
|
|
|
# Install pre-compiled Anki.
|
|
|
|
FROM python:${PYTHON_VERSION}-slim as installer
|
|
|
|
WORKDIR /opt/anki/
|
updates to the build process and binary bundles
All platforms:
- rename scripts/ to tools/: Bazelisk expects to find its wrapper script
(used by the Mac changes below) in tools/. Rather than have a separate
scripts/ and tools/, it's simpler to just move everything into tools/.
- wheel outputs and binary bundles now go into .bazel/out/dist. While
not technically Bazel build products, doing it this way ensures they get
cleaned up when 'bazel clean' is run, and it keeps them out of the source
folder.
- update to the latest Bazel
Windows changes:
- bazel.bat has been removed, and tools\setup-env.bat has been added.
Other scripts like .\run.bat will automatically call it to set up the
environment.
- because Bazel is now on the path, you can 'bazel test ...' from any
folder, instead of having to do \anki\bazel.
- the bat files can handle being called from any working directory,
so things like running "\anki\tools\python" from c:\ will work.
- build installer as part of bundling process
Mac changes:
- `arch -arch x86_64 bazel ...` will now automatically use a different
build root, so that it is cheap to switch back and forth between archs
on a new Mac.
- tools/run-qt* will now automatically use Rosetta
- disable jemalloc in Mac x86 build for now, as it won't build under
Rosetta (perhaps due to its build scripts using $host_cpu instead of
$target_cpu)
- create app bundle as part of bundling process
Linux changes:
- remove arm64 orjson workaround in Linux bundle, as without a
readily-available, relatively distro-agonstic PyQt/Qt build
we can use, the arm64 Linux bundle is of very limited usefulness.
- update Docker files for release build
- include fcitx5 in both the qt5 and qt6 bundles
- create tarballs as part of the bundling process
2022-01-30 01:50:14 +01:00
|
|
|
COPY --from=build /opt/anki/wheels/ wheels/
|
2021-10-15 02:41:15 +02:00
|
|
|
# Use virtual environment.
|
|
|
|
RUN python -m venv venv \
|
|
|
|
&& ./venv/bin/python -m pip install --no-cache-dir setuptools wheel \
|
|
|
|
&& ./venv/bin/python -m pip install --no-cache-dir /opt/anki/wheels/*.whl
|
|
|
|
|
|
|
|
# We use another build stage here so we don't include the wheels in the final image.
|
|
|
|
FROM python:${PYTHON_VERSION}-slim as final
|
|
|
|
COPY --from=installer /opt/anki/venv /opt/anki/venv
|
|
|
|
ENV PATH=/opt/anki/venv/bin:$PATH
|
|
|
|
# Install run-time dependencies.
|
|
|
|
RUN apt-get update \
|
|
|
|
&& apt-get install --yes --no-install-recommends \
|
updates to the build process and binary bundles
All platforms:
- rename scripts/ to tools/: Bazelisk expects to find its wrapper script
(used by the Mac changes below) in tools/. Rather than have a separate
scripts/ and tools/, it's simpler to just move everything into tools/.
- wheel outputs and binary bundles now go into .bazel/out/dist. While
not technically Bazel build products, doing it this way ensures they get
cleaned up when 'bazel clean' is run, and it keeps them out of the source
folder.
- update to the latest Bazel
Windows changes:
- bazel.bat has been removed, and tools\setup-env.bat has been added.
Other scripts like .\run.bat will automatically call it to set up the
environment.
- because Bazel is now on the path, you can 'bazel test ...' from any
folder, instead of having to do \anki\bazel.
- the bat files can handle being called from any working directory,
so things like running "\anki\tools\python" from c:\ will work.
- build installer as part of bundling process
Mac changes:
- `arch -arch x86_64 bazel ...` will now automatically use a different
build root, so that it is cheap to switch back and forth between archs
on a new Mac.
- tools/run-qt* will now automatically use Rosetta
- disable jemalloc in Mac x86 build for now, as it won't build under
Rosetta (perhaps due to its build scripts using $host_cpu instead of
$target_cpu)
- create app bundle as part of bundling process
Linux changes:
- remove arm64 orjson workaround in Linux bundle, as without a
readily-available, relatively distro-agonstic PyQt/Qt build
we can use, the arm64 Linux bundle is of very limited usefulness.
- update Docker files for release build
- include fcitx5 in both the qt5 and qt6 bundles
- create tarballs as part of the bundling process
2022-01-30 01:50:14 +01:00
|
|
|
libasound2 \
|
|
|
|
libdbus-1-3 \
|
|
|
|
libfontconfig1 \
|
|
|
|
libfreetype6 \
|
|
|
|
libgl1 \
|
|
|
|
libglib2.0-0 \
|
|
|
|
libnss3 \
|
|
|
|
libxcb-icccm4 \
|
|
|
|
libxcb-image0 \
|
|
|
|
libxcb-keysyms1 \
|
|
|
|
libxcb-randr0 \
|
|
|
|
libxcb-render-util0 \
|
|
|
|
libxcb-shape0 \
|
|
|
|
libxcb-xinerama0 \
|
|
|
|
libxcb-xkb1 \
|
|
|
|
libxcomposite1 \
|
|
|
|
libxcursor1 \
|
|
|
|
libxi6 \
|
|
|
|
libxkbcommon0 \
|
|
|
|
libxkbcommon-x11-0 \
|
|
|
|
libxrandr2 \
|
|
|
|
libxrender1 \
|
|
|
|
libxtst6 \
|
2021-10-15 02:41:15 +02:00
|
|
|
&& rm -rf /var/lib/apt/lists/*
|
|
|
|
# Add non-root user.
|
|
|
|
RUN useradd --create-home anki
|
|
|
|
USER anki
|
|
|
|
WORKDIR /work
|
|
|
|
ENTRYPOINT ["/opt/anki/venv/bin/anki"]
|
|
|
|
LABEL maintainer="Jakub Kaczmarzyk <jakub.kaczmarzyk@gmail.com>"
|