Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCI Runtime Failed when building QField via docker image #4233

Closed
KianL1 opened this issue Apr 26, 2023 · 2 comments
Closed

OCI Runtime Failed when building QField via docker image #4233

KianL1 opened this issue Apr 26, 2023 · 2 comments

Comments

@KianL1
Copy link

KianL1 commented Apr 26, 2023

Describe the issue

I get an error when I try to build Qfield using a docker image, on all triplets

Reproduction steps

Steps to reproduce the behavior:

  1. Open Docker

  2. Create a New Dev Environment pulling from Qfield git source

  3. Run the Docker Container

  4. Check Images tab to see if Qfield_and_dev has been created

image

  1. Open Git Bash

  2. Pull Qfield Source, update submodules

  3. Run Docker Build Script

Expected behavior

To build a Qfield Apk from a docker image

Observed behavior

Recieve an error at step [7/13]

$ triplet=arm-android ./scripts/build.sh
#2 [internal] load .dockerignore
#2 sha256:68bba8f5ff89f3d20be9f003a602bdae984b5d3a60b1fbe6d1e7cb4aa7a06a9d
#2 transferring context: 2B 0.0s done
#2 DONE 0.1s

#1 [internal] load build definition from Dockerfile
#1 sha256:74680fb93ff107cb7bc5c5650f6ac858b080ef18de686bcc8ce4e5937ac25d50
#1 transferring dockerfile: 32B 0.1s done
#1 DONE 0.1s

#3 [internal] load metadata for docker.io/library/ubuntu:22.04
#3 sha256:c98673cf9ef937b1780d76523bbd6cd77884d860bede4bf0d006ae7d8201e8a5
#3 ...

#4 [auth] library/ubuntu:pull token for registry-1.docker.io
#4 sha256:0bb3b6e26bc3679489fbbcd85b756904c0085acc816cca6c54096be6da805b13
#4 DONE 0.0s

#3 [internal] load metadata for docker.io/library/ubuntu:22.04
#3 sha256:c98673cf9ef937b1780d76523bbd6cd77884d860bede4bf0d006ae7d8201e8a5
#3 DONE 1.1s

#17 [ 1/13] FROM docker.io/library/ubuntu:22.04@sha256:67211c14fa74f070d27cc59d69a7fa9aeff8e28ea118ef3babc295a0428a6d21
#17 sha256:f72a6a820aa23b1276a94e898264672899d8e77e6cb01cd4bf7c8d1158ad229b
#17 DONE 0.0s

#18 [internal] load build context
#18 sha256:c1de799a3d00d5721d88073f6fdda029fd5ecb3681aa7a41854b0ce5e96b6309
#18 transferring context: 673B 0.0s done
#18 DONE 0.1s

#5 [ 2/13] RUN dpkg --add-architecture i386 && apt-get update -yqq && apt-get install -y   curl   expect   git   make   libc6:i386   libgcc1:i386   libncurses5:i386   libstdc++6:i386   zlib1g:i386   openjdk-11-jdk   wget   unzip   vim   openssh-client   locales   cmake   git   build-essential   curl   zip   unzip   tar   libarchive-tools   autoconf   python3-pip   pkg-config   libtool   flex   bison   ninja-build   jq   dirmngr   gnupg   apt-transport-https   ca-certificates   software-properties-common   && apt-get clean   && rm -rf /var/lib/apt/lists/*   && localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias en_US.UTF-8
#5 sha256:d2a66c48c5cf3f8d0f97409593f7c2c7567b310ea58dcd220dca5328632c0f3d
#5 CACHED

#6 [ 3/13] RUN groupadd android && useradd -d /opt/android-sdk-linux -g android -u 1000 android
#6 sha256:aa2c57601ebc188881142ad0016f2dd27af671d5bef2663985047e48e9f796a4
#6 CACHED

#7 [ 4/13] COPY tools /opt/tools
#7 sha256:54dc6536f6fd02f1574775691ecc2b3a60b73f4c12a55b345b929ba2de5c0489
#7 CACHED

#8 [ 5/13] COPY licenses /opt/licenses
#8 sha256:9eb9360545ad9904aeee0a3c3ed0f7266f220f25a309195d3a6c7e3c3311252a
#8 CACHED

#9 [ 6/13] WORKDIR /opt/android-sdk-linux
#9 sha256:4b606e2c8fd497c15a70eeb3cda903e93d7d76678d8ef8af2cd7b2d20ec6113b
#9 CACHED

#10 [ 7/13] RUN /opt/tools/entrypoint.sh built-in
#10 sha256:a9d150af26bc160be9c4e9edf67c38dc1a758c685d8b271204cc80d43ea99f65
#10 0.348 /bin/sh: 1: /opt/tools/entrypoint.sh: not found
#10 ERROR: executor failed running [/bin/sh -c /opt/tools/entrypoint.sh built-in]: exit code: 127
------
 > [ 7/13] RUN /opt/tools/entrypoint.sh built-in:
------
executor failed running [/bin/sh -c /opt/tools/entrypoint.sh built-in]: exit code: 127
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=ffac63cddf83
TERM=xterm
ANDROID_SDK_HOME=/opt/android-sdk-linux
ANDROID_SDK_ROOT=/opt/android-sdk-linux
ANDROID_HOME=/opt/android-sdk-linux
ANDROID_SDK=/opt/android-sdk-linux
DEBIAN_FRONTEND=noninteractive
LANG=en_US.UTF-8
ANDROID_NDK_HOME=/opt/android-sdk-linux/ndk/22.1.7171670
ANDROID_NDK_VERSION=22.1.7171670
HOME=/root
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "C:/Program Files/Git/usr/src/qfield/scripts/build-vcpkg.sh": stat C:/Program Files/Git/usr/src/qfield/scripts/build-vcpkg.sh: no such file or directory: unknown.

Desktop (please complete the following information)

  • OS: [e.g. Windows]
  • QGIS Version [e.g. 3.22.0]
  • QFieldSync Version [e.g.4.0.0]

Additional information

  • Problem started happening recently, didn't happen in an older version of QField: Yes
  • Problem can be reliably reproduced, doesn't happen randomly: Yes
  • Problem happens with all files and projects, not only some files or projects: Yes
@m-kuhn
Copy link
Member

m-kuhn commented May 4, 2023

It looks like it tries to run C:/Program Files/Git/usr/src/qfield/scripts/build-vcpkg.sh inside the docker environment. I.e. it is a windows path, used in a linux environment.

Normally this script is called from here https://github.com/opengisch/QField/blob/master/scripts/build.sh#L34 where the path is hardcoded.
I am not sure why it is trying to call this script in step 7 (https://github.com/opengisch/QField/blob/master/.docker/android_dev/Dockerfile#L65)

  • Are you using the latest version of the QField source code (master branch)?
  • Can you try this on a linux machine (might even be possible in WSL, I don't have much experience, I could imagine it's a windows specific issue

@m-kuhn m-kuhn added the feedback label May 4, 2023
@github-actions
Copy link
Contributor

The QField project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale label May 19, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants