I've been trying to create a build.yml in Github Actions for one of my projects to convert into android, but if I try to use one of the built-in Github Actions to get buildozer working, it always returns the same error. Here's the code I put in my build.yml that resulted in the error: - name: Build with Buildozer uses: ArtemSBulgakov/buildozer-action@v1 id: buildozer with: workdir: . buildozer_version: stable When I try to run it, I get this error: #0 building with "default" instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: 696B done #1 DONE 0.0s #2 [auth] kivy/buildozerull token for registry-1.docker.io #2 DONE 0.0s #3 [internal] load metadata for docker.io/kivy/buildozer:latest #3 ERROR: encountered unknown type application/vnd.oci.image.layer.v1.tar+gzip; children may not be fetched ------ > [internal] load metadata for docker.io/kivy/buildozer:latest: ------ Dockerfile:1 -------------------- 1 | >>> FROM kivy/buildozer:latest 2 | # See https://github.com/kivy/buildozer/blob/master/Dockerfile 3 | -------------------- ERROR: failed to solve: kivy/buildozer:latest: failed to resolve source metadata for docker.io/kivy/buildozer:latest: encountered unknown type application/vnd.oci.image.layer.v1.tar+gzip; children may not be fetched Warning: Docker build failed with exit code 1, back off 1.505 seconds before retry. /usr/bin/docker build -t 6d243c:7b13c0781cdd4f56a4e9847b141a9ed5 -f "/home/runner/work/_actions/ArtemSBulgakov/buildozer-action/v1/Dockerfile" "/home/runner/work/_actions/ArtemSBulgakov/buildozer-action/v1" It tries three times but fails. I haven't had any luck resolving this issue, but I think it might be a problem from docker itself. If anybody knows, I would really appreciate it if you could let me know what I should do from here. Note: I already tried using other pre-made Github Actions and even tried installing and running buildozer myself, but I keep running into a lot of problems and I'm not very knowledgeable when it comes to buildozer, p4a and Github. Continue reading...
