docker-android-sdk

<div align="center"> <h3 align="center">docker-android-sdk</h3> Docker image containing the <a href="https://developer.android.com/tools">Android SDK</a> · <a href="https://github.com/mindrunner/docker-android-sdk/issues">Report Bug</a> · <a href="https://github.com/mindrunner/docker-android-sdk/issues">Request Feature</a> · </div> <details> <summary>Table of Contents</summary> <ol> <li> <a href="#announcement">Announcement</a> <a href="#about-the-project">About The Project</a> <ul> <li><a href="#tags">Tags</a></li> <li><a href="#built-with">Built With</a></li> </ul> </li> <li> <a href="#usage">Usage</a> <ul> <li><a href="#compile-and-run">Compile and Run</a></li> </ul> </li> <li><a href="#roadmap">Roadmap</a></li> <li><a href="#contributing">Contributing</a></li> <li><a href="#disclaimer">Disclaimer</a></li> <li><a href="#license">License</a></li> <li><a href="#donations">Donations</a></li> </ol> </details>

Announcement

Builds

The build pipeline was migrated to github actions. (see below for available tags)
Nightly build are suffixed with the date

Major Changes

JDK was upgraded from 11 to 17

2023 Spring Cleaning

https://github.com/mindrunner/docker-android-sdk/issues/92

(<a href="#readme-top">back to top</a>)

About The Project

This repository contains Dockerfiles to create Docker images containing the Android SDK. There are two flavors for different use cases (lazydl, standalone) and two different linux bases (ubuntu, alpine). Feel free to chose which one suits you best.

Ubuntu The officially supported Linux distribution for Android SDK builds. Use this one if you are unsure.

Alpine More lightweight Linux Distribution optimized for docker containers. (Not officially supported / Android Emulator broken)

Standalone This is the standard expected behaviour. The Android SDK is integrated in the docker image. Use this in your android build on CircleCI, Bitbucket Pipelines, or any other docker enabled CI.

Lazydl Indeed, there is a lack of documentation and it might be not really intuitive to use the image in this way. The idea is to have two containers for the build process. One of which is the building container executing the actual build. The other one is the sdk-data container, which downloads the whole SDK into a named docker volume which is shared between both containers.

Lazydl can also be used to download and prepare a custom list of sdk components if you only need a portion of the sdk. Just mount a volume in at runtime pointing a list named package-list-minimal.txt into /opt/tools/package-list-minimal.txt and then run /opt/tools/entrypoint.sh built-in. You can also use Lazydl as a base for your own custom image.

(<a href="#readme-top">back to top</a>)

Built With

(<a href="#readme-top">back to top</a>)

Usage

TBD.

Compile and run

TBD.

Roadmap

[] TBD.

See the open issues for a full list of proposed features (and known issues).

(<a href="#readme-top">back to top</a>)

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!