LBRYCommunity/buildozer
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
buildozer/Dockerfile

81 lines
2 KiB
Docker
Raw Normal View History

Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
# Dockerfile for providing buildozer
Updates system requirements needed to build recipes Makes it possible to build Android APKs directly from Docker. Tested by building sucessfully both: * kivy-garden/garden.zbarcam (20190303) * AndreMiras/EtherollApp (20190217) After building the image with: ``` docker build --tag=kivy/buildozer . ``` The following command was used to build the Android APK: ``` docker run \ --volume "$HOME/.buildozer":/home/user/.buildozer \ --volume "$(pwd)":/home/user/hostcwd \ kivy/buildozer android debug ``` Note the system dependencies were also sorted alphabetical to ease maintenance. Later more dependencies can be added if needed to build a given recipe.
2019-03-10 23:11:10 +01:00
#
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
# Build with:
Updates system requirements needed to build recipes Makes it possible to build Android APKs directly from Docker. Tested by building sucessfully both: * kivy-garden/garden.zbarcam (20190303) * AndreMiras/EtherollApp (20190217) After building the image with: ``` docker build --tag=kivy/buildozer . ``` The following command was used to build the Android APK: ``` docker run \ --volume "$HOME/.buildozer":/home/user/.buildozer \ --volume "$(pwd)":/home/user/hostcwd \ kivy/buildozer android debug ``` Note the system dependencies were also sorted alphabetical to ease maintenance. Later more dependencies can be added if needed to build a given recipe.
2019-03-10 23:11:10 +01:00
# docker build --tag=kivy/buildozer .
PR#775 - docker from current git
2018-12-28 12:30:39 +01:00
#
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
# In order to give the container access to your current working directory
# it must be mounted using the --volume option.
# Run with (e.g. `buildozer --version`):
Updates system requirements needed to build recipes Makes it possible to build Android APKs directly from Docker. Tested by building sucessfully both: * kivy-garden/garden.zbarcam (20190303) * AndreMiras/EtherollApp (20190217) After building the image with: ``` docker build --tag=kivy/buildozer . ``` The following command was used to build the Android APK: ``` docker run \ --volume "$HOME/.buildozer":/home/user/.buildozer \ --volume "$(pwd)":/home/user/hostcwd \ kivy/buildozer android debug ``` Note the system dependencies were also sorted alphabetical to ease maintenance. Later more dependencies can be added if needed to build a given recipe.
2019-03-10 23:11:10 +01:00
# docker run \
# --volume "$HOME/.buildozer":/home/user/.buildozer \
# --volume "$(pwd)":/home/user/hostcwd \
# kivy/buildozer --version
#
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
# Or for interactive shell:
Updates system requirements needed to build recipes Makes it possible to build Android APKs directly from Docker. Tested by building sucessfully both: * kivy-garden/garden.zbarcam (20190303) * AndreMiras/EtherollApp (20190217) After building the image with: ``` docker build --tag=kivy/buildozer . ``` The following command was used to build the Android APK: ``` docker run \ --volume "$HOME/.buildozer":/home/user/.buildozer \ --volume "$(pwd)":/home/user/hostcwd \ kivy/buildozer android debug ``` Note the system dependencies were also sorted alphabetical to ease maintenance. Later more dependencies can be added if needed to build a given recipe.
2019-03-10 23:11:10 +01:00
# docker run --interactive --tty --rm \
# --volume "$HOME/.buildozer":/home/user/.buildozer \
# --volume "$(pwd)":/home/user/hostcwd \
# --entrypoint /bin/bash \
# kivy/buildozer
#
# If you get a `PermissionError` on `/home/user/.buildozer/cache`,
# try updating the permissions from the host with:
# sudo chown $USER -R ~/.buildozer
# Or simply recreate the directory from the host with:
# rm -rf ~/.buildozer && mkdir ~/.buildozer
PR#775 - docker from current git
2018-12-28 12:30:39 +01:00
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
FROM ubuntu:18.04
ENV USER="user"
ENV HOME_DIR="/home/${USER}"
ENV WORK_DIR="${HOME_DIR}/hostcwd" \
Various Dockerfile improvements - installs cutting edge version from current source - removes outdated java version fixes - migrates to host Python3 - verifies the image builds and run via Travis - fixes minor linting: "E117 over-indented"
2019-03-08 01:18:04 +01:00
SRC_DIR="${HOME_DIR}/src" \
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
PATH="${HOME_DIR}/.local/bin:${PATH}"
# configures locale
RUN apt update -qq > /dev/null && \
apt install -qq --yes --no-install-recommends \
locales && \
locale-gen en_US.UTF-8
ENV LANG="en_US.UTF-8" \
LANGUAGE="en_US.UTF-8" \
LC_ALL="en_US.UTF-8"
Updates system requirements needed to build recipes Makes it possible to build Android APKs directly from Docker. Tested by building sucessfully both: * kivy-garden/garden.zbarcam (20190303) * AndreMiras/EtherollApp (20190217) After building the image with: ``` docker build --tag=kivy/buildozer . ``` The following command was used to build the Android APK: ``` docker run \ --volume "$HOME/.buildozer":/home/user/.buildozer \ --volume "$(pwd)":/home/user/hostcwd \ kivy/buildozer android debug ``` Note the system dependencies were also sorted alphabetical to ease maintenance. Later more dependencies can be added if needed to build a given recipe.
2019-03-10 23:11:10 +01:00
# system requirements to build most of the recipes
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
RUN apt install -qq --yes --no-install-recommends \
Updates system requirements needed to build recipes Makes it possible to build Android APKs directly from Docker. Tested by building sucessfully both: * kivy-garden/garden.zbarcam (20190303) * AndreMiras/EtherollApp (20190217) After building the image with: ``` docker build --tag=kivy/buildozer . ``` The following command was used to build the Android APK: ``` docker run \ --volume "$HOME/.buildozer":/home/user/.buildozer \ --volume "$(pwd)":/home/user/hostcwd \ kivy/buildozer android debug ``` Note the system dependencies were also sorted alphabetical to ease maintenance. Later more dependencies can be added if needed to build a given recipe.
2019-03-10 23:11:10 +01:00
autoconf \
automake \
build-essential \
ccache \
cmake \
gettext \
git \
libffi-dev \
libltdl-dev \
libtool \
openjdk-8-jdk \
patch \
pkg-config \
python2.7 \
python3-pip \
python3-setuptools \
sudo \
unzip \
zip \
zlib1g-dev
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
# prepares non root env
RUN useradd --create-home --shell /bin/bash ${USER}
# with sudo access and no password
RUN usermod -append --groups sudo ${USER}
RUN echo "%sudo ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
USER ${USER}
WORKDIR ${WORK_DIR}
Various Dockerfile improvements - installs cutting edge version from current source - removes outdated java version fixes - migrates to host Python3 - verifies the image builds and run via Travis - fixes minor linting: "E117 over-indented"
2019-03-08 01:18:04 +01:00
COPY --chown=user:user . ${SRC_DIR}
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
# installs buildozer and dependencies
Various Dockerfile improvements - installs cutting edge version from current source - removes outdated java version fixes - migrates to host Python3 - verifies the image builds and run via Travis - fixes minor linting: "E117 over-indented"
2019-03-08 01:18:04 +01:00
RUN pip3 install --user Cython==0.28.6 ${SRC_DIR}
Buildozer Dockerfile, fixes #589 Installs buildozer and dependencies, documents usage. To build the image you first need to `cd` to where the `Dockerfile` is, then run: ```sh docker build --tag=buildozer . ``` Then you can use the container e.g. with: ```sh docker run --volume "$(pwd)":/home/user/hostcwd buildozer --help ``` The above command mounts host current working directory in container using `--volume` option. Also added workaround for #625
2018-06-18 21:54:54 +02:00
ENTRYPOINT ["buildozer"]
Reference in a new issue Copy permalink