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

Docker build is broken #3323

Closed
vorburger opened this issue Nov 3, 2020 · 2 comments
Closed

Docker build is broken #3323

vorburger opened this issue Nov 3, 2020 · 2 comments
Assignees

Comments

@vorburger
Copy link
Member

Building the Docker image for this project, following our documentation on https://github.com/openMF/community-app#docker, currently fails.

Locally for me, trying right now, the error is (I'm using podman instead of docker so your error could be slightly different):

$ docker build -t mifos-community-app .
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
STEP 1: FROM timbru31/ruby-node:2.7 AS builder
STEP 2: RUN mkdir /usr/src/app
2020-11-03T20:24:56.000558796Z: exec container process `/bin/sh`: Exec format error
STEP 3: FROM nginx:1.19.2
Error: error building at STEP "RUN mkdir /usr/src/app": error while running runtime: exit status 1

On Docker Hub it also fails right now, the error there is:

Starting build of index.docker.io/openmf/community-app:latest...
Step 1/16 : FROM timbru31/ruby-node:2.7 as builder
---> 07ca45e44f08
Step 2/16 : RUN mkdir /usr/src/app
---> Running in 58d3f788dc27
�[91mstandard_init_linux.go:211: exec user process caused "exec format error"
�[0m
Removing intermediate container 58d3f788dc27
The command '/bin/bash -o pipefail -c mkdir /usr/src/app' returned a non-zero code: 1
@vorburger vorburger self-assigned this Nov 3, 2020
@vorburger
Copy link
Member Author

I've figured out what's causing this... it's an issue that's not completely trivial to spot in the timbru31/ruby-node:2.7 base image.

I'll open an issue with details about it in that project. It needs to either be fixed there - or we change our base image.

@vorburger
Copy link
Member Author

This problem was just fixed in timbru31/docker-ruby-node#564 (very, impressive; thanks again @timbru31)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant