oupala

It seems that the url where your Dockerfile is getting the *repo* binary is only proposing *repo* 1.13.7: https://github.com/jfloff/docker-lineageos/blob/61ba7feca3946803fb182061df13f5351bee0cf8/Dockerfile#L85 This is why a simple rebuild of the docker-lineageos image does...

In fact, I think that there is a misunderstanding about repo. repo is composed of 2 parts: repo and repo laucher. - repo is available as version 1.13.x, 2.2, 2.3,...

I made some extensive testing about this image. ```bash $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE jfloff/lineageos latest cf6b995b758c 4 months ago 1.03GB $ docker run -it --rm...

I tried to change the `FROM` image of the Dockerfile from `openjdk:8` to `openjdk:8u242-slim-buster`. The problem is that the image does not build any more: the `libesd0-dev` package is missing...

`unzip` was also missing. Here is the current diff of my Dockerfile: ```diff $ git diff diff --git a/Dockerfile b/Dockerfile index 28245ce..a0fe27d 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,4 +1,4...

I get an error about another missing library: > error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory I think I can't go...

Is there any hope to get some help? Is there anyone having an idea of the current version of *repo*? @jfloff Have you a few minutes to help me just...

In [this comment (22 Oct 2019)](https://github.com/jfloff/docker-lineageos/issues/15#issuecomment-544918601), I was saying that repo was only available in version 1.13.7 in [the *repo* repo](https://gerrit.googlesource.com/git-repo/). This repo is currently proposing a lot a releases...

I'm not sure if the device codename should be `espressowifi` or `espresso-common` as the binary blobs of [espressowifi](https://wiki.lineageos.org/devices/espressowifi/) and [espresso3g](https://wiki.lineageos.org/devices/espresso3g/) have been merged into [espresso-common](https://github.com/TheMuppets/proprietary_vendor_samsung/tree/lineage-16.0/espresso-common). See the pull request [p31xx/p51xx:...

It is a good idea. I have not tested it yet. I'll do that and I'll come back here with the answer.