arm64 compatible docker #4

cyrrelsneer · 2021-05-03T16:27:29Z

Hi,

it would be most welcome to get a docker image that is arm64 compatible.

cupcakearmy · 2021-05-03T22:18:35Z

Arm build now available, as i don't have a pi flying around rn could you verify it working? Build times went from 9min to 45 though 😆🙈
maybe should look at caching the rust stuff

cyrrelsneer · 2021-05-04T16:42:53Z

Hi,

thanks for that, appreciate it.
I just pulled it with
docker pull cupcakearmy/cryptgeon:latest

works fine
but when firing up the container, it says "standard_init_linux.go:219: exec user process caused: no such file or directory"

that usually happens with wrong architecture (cryptgeon_memcached_1 is running, app_1 stopping)

would mind having a look at that?

cupcakearmy · 2021-05-04T17:28:36Z

Mhh I see, could you clone the repo and build the container locally and see what happens?

git clone https://github.com/cupcakearmy/cryptgeon.git
docker-compose up
# Go to http://localhost

cyrrelsneer · 2021-05-04T17:38:31Z

after some minutes, it stops wit this:
OK: 211 MiB in 53 packages Removing intermediate container 799af584ab77 ---> c94b0fa4aef3 Step 9/17 : COPY ./Cargo* . ERROR: Service 'app' failed to build: When using COPY with more than one source file, the destination must be a directory and end with a /

cupcakearmy · 2021-05-04T17:43:02Z

I see

FROM node:16-alpine as CLIENT

WORKDIR /tmp
COPY ./client ./

RUN npm ci
RUN npm run build

FROM rust:1.51-alpine as RUST

WORKDIR /tmp
RUN apk add libc-dev openssl-dev alpine-sdk
COPY ./Cargo* ./
COPY ./src ./src

RUN cargo build --release

FROM scratch

WORKDIR /app
COPY --from=RUST /tmp/target/release/cryptgeon .
COPY --from=CLIENT /tmp/build ./client/build

ENV MEMCACHE=memcached:11211

ENTRYPOINT [ "/app/cryptgeon" ]

can you try with this Dockerfile?

cupcakearmy · 2021-05-04T17:43:36Z

Proably have to run docker-compose build before running docker-compose up

cyrrelsneer · 2021-05-04T19:08:41Z

What I've done now:

I deleted the directory locally
git clone https://github.com/cupcakearmy/cryptgeon.git
changed your Dockerfile accordingly
docker-compose build
docker-compose up

Took quite a while, but... error:
Successfully built c623acf1a101 Successfully tagged cryptgeon_app:latest ubuntu@ubuntu:~/cryptgeon/cryptgeon$ docker-compose up Creating cryptgeon_memcached_1 ... done Creating cryptgeon_app_1 ... done Attaching to cryptgeon_memcached_1, cryptgeon_app_1 app_1 | standard_init_linux.go:219: exec user process caused: no such file or directory cryptgeon_app_1 exited with code 1

cupcakearmy · 2021-05-04T19:23:29Z

Uff, thats some trial and error xD

FROM node:16-alpine as CLIENT

WORKDIR /tmp
COPY ./client ./

RUN npm ci
RUN npm run build

FROM rust:1.51-alpine as RUST

WORKDIR /tmp
RUN apk add libc-dev openssl-dev alpine-sdk
COPY ./Cargo* ./
COPY ./src ./src

RUN cargo build --release

FROM alpine

WORKDIR /app
COPY --from=RUST /tmp/target/release/cryptgeon .
COPY --from=CLIENT /tmp/build ./client/build

ENV MEMCACHE=memcached:11211

ENTRYPOINT [ "/app/cryptgeon" ]

Could you try this file? (don't neet to delete the local copy)

cyrrelsneer · 2021-05-04T21:18:54Z

Can't blame you if you want to stop ;)

Starting cryptgeon_memcached_1 ... done Recreating cryptgeon_app_1 ... done Attaching to cryptgeon_memcached_1, cryptgeon_app_1 app_1 | standard_init_linux.go:219: exec user process caused: no such file or directory cryptgeon_app_1 exited with code 1

cupcakearmy · 2021-05-04T21:21:27Z

Mhhh thats weird, maybe I'll dust out some old pi and do some debugging. Can't promise anything

cupcakearmy · 2021-05-04T21:22:04Z

You are arm64 right?

cyrrelsneer · 2021-05-04T21:33:04Z

uname -a
Linux ubuntu 5.4.0-1034-raspi #37-Ubuntu SMP PREEMPT Mon Apr 12 23:14:49 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

That's Ubuntu 64Bit on my Rpi4

cupcakearmy · 2021-05-04T23:31:00Z

Yeah aarch64 ist arm64. Thanks for the info

cyrrelsneer · 2021-05-05T06:34:52Z

never mind if it's too much work, appreciate your help but it is maybe not worth wasting your hours on that topic.
But again -thanks!

cupcakearmy · 2021-05-05T08:40:28Z

I'll remove the arm images for now

ThisIsBenny · 2021-05-16T10:12:14Z

Hi, this is how i build a multi arch Image with GitHub Workflows:

https://github.com/ThisIsBenny/n8n/blob/main/.github/workflows/build_images.yml

Result:

cupcakearmy · 2021-05-16T10:32:48Z

We had arm builds (https://github.com/cupcakearmy/cryptgeon/blob/cfe525f274b6e364f3d9b2a953434bd1cad18bbe/.github/workflows/docker.yml), but they did have some runtime errors, have not found the time yet to check on a raspi xD

ThisIsBenny · 2021-05-16T11:29:59Z

We had arm builds (https://github.com/cupcakearmy/cryptgeon/blob/cfe525f274b6e364f3d9b2a953434bd1cad18bbe/.github/workflows/docker.yml), but they did have some runtime errors, have not found the time yet to check on a raspi xD

I think the issue is that you are not referencing to the buildx builder which you create in the step before the build command. Try:

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
        id: buildx
…
      - name: Build and push
        id: docker_build
        uses: docker/build-push-action@v2
        with:
          builder: ${{ steps.buildx.outputs.name }}
          platforms: linux/amd64,linux/arm64
          push: true
          tags: ${{ steps.meta.outputs.tags }}

Without the reference, the build will be happen with the normal builder which doesn‘t support multi arch build until now.

You can also add some logging, for example for the Rust and the alpine image:

FROM <image-name>
ARG TARGETPLATFORM
ARG BUILDPLATFORM
RUN echo "I am running on $BUILDPLATFORM, building for $TARGETPLATFORM"

cupcakearmy · 2021-05-19T09:29:52Z

I followed the official docs, but they might be outdated
https://github.com/docker/build-push-action/blob/master/docs/advanced/multi-platform.md

Will try with default install https://github.com/docker/setup-buildx-action#install-by-default

cupcakearmy · 2021-05-19T11:19:50Z

@cyrrelsneer can you try 1.1.1 version?

vladosam · 2021-12-23T07:34:26Z

Hi, is aarch64 suported now? I'm getting this error on Ubuntu aarch64 VPS server.
app_1 | standard_init_linux.go:228: exec user process caused: no such file or directory

cupcakearmy · 2021-12-23T09:38:06Z

Very good question. I have no arm machine to verify it unfortunately :/ Maybe I could rent some VMs and test it out if I find time.

I know the error message, it's when building go with c bindings and then running it on FROM:scratch. However the question is:

Why is there go code running?
And why does this only happen on arm....

TBH, I'm quite confused

cupcakearmy · 2021-12-23T09:55:54Z

@vladosam could you try building and running the docker file with CGO_ENABLED=0?

FROM node:16-alpine as CLIENT

ENV CGO_ENABLED=0
WORKDIR /tmp
COPY ./client ./

RUN npm install -g pnpm
RUN pnpm install
RUN pnpm run build

FROM rust:1.51-alpine as RUST

ENV CGO_ENABLED=0
WORKDIR /tmp
RUN apk add libc-dev openssl-dev alpine-sdk
COPY ./Cargo* ./
COPY ./src ./src

RUN cargo build --release

FROM scratch

WORKDIR /app
COPY --from=RUST /tmp/target/release/cryptgeon .
COPY --from=CLIENT /tmp/build ./client/build

ENV MEMCACHE=memcached:11211

EXPOSE 5000

ENTRYPOINT [ "/app/cryptgeon" ]

vladosam · 2021-12-23T10:40:43Z

I created Dockerfile but i can't build it.
docker build -t cryptgeon .

Step 1/21 : FROM node:16-alpine as CLIENT
 ---> 8074a83d0ba9
Step 2/21 : ENV CGO_ENABLED=0
 ---> Using cache
 ---> 2b6a1ef23e2a
Step 3/21 : WORKDIR /tmp
 ---> Using cache
 ---> dee5505ad804
Step 4/21 : COPY ./client ./
COPY failed: file not found in build context or excluded by .dockerignore: stat client: file does not exist

cupcakearmy · 2021-12-23T10:52:58Z

Are you sure you are in the right context? step 4 cannot fail really

cupcakearmy · 2021-12-23T10:55:06Z

Otherwise try the following steps:

Clone a fresh instance of the repo
Change FROM scratch to FROM alpine in the Dockerfile and try to build

vladosam · 2021-12-23T11:05:58Z

You where right. I was in wrong directory. But issue is still there.

docker run -it cryptgeon
standard_init_linux.go:228: exec user process caused: no such file or directory

cupcakearmy · 2021-12-23T11:50:11Z

Can you try with the comment before? #4 (comment)

vladosam · 2021-12-23T11:57:00Z

You mean docker-compose up? I'll try it later.

cupcakearmy · 2021-12-23T14:30:38Z

Yeah with alpine instead of from scratch in the dockerfile

vladosam · 2021-12-23T14:58:24Z

Nope.

Attaching to cryptgeon_memcached_1, cryptgeon_app_1
app_1        | standard_init_linux.go:228: exec user process caused: no such file or directory

0xSh1v4 · 2021-12-30T18:27:44Z

Is there any update on this? I would like to have this arm64 support as well.

cupcakearmy · 2021-12-30T18:42:09Z

Is there any update on this? I would like to have this arm64 support as well.

Unfortunately I'm kind of powerless. I need you guys with arm to test it.

vladosam · 2021-12-30T19:02:48Z

Just say what to try.

0xSh1v4 · 2021-12-30T19:05:04Z

Is there any update on this? I would like to have this arm64 support as well.

Unfortunately I'm kind of powerless. I need you guys with arm to test it.

Let me know what to try. I would try as well. Thanks

cupcakearmy · 2021-12-30T20:39:18Z

@vladosam @0xSh1v4 apparently the docker image does not work on arm.

If you could get it to work I could commit the changes and release docker images for everyone.

Some things that I would try is running form alpine and not from scracth in the Dockerfile.

To build it you can just use docker-compoe up --build

vladosam · 2021-12-31T07:53:06Z

I tried that before and it didn't work.

cupcakearmy · 2022-01-03T00:54:49Z

Could you try the latest release?

0xSh1v4 · 2022-01-03T10:47:59Z

Could you try the latest release?
I got the following error:
No log line matching the '' filter

cupcakearmy self-assigned this May 3, 2021

cupcakearmy added the enhancement New feature or request label May 3, 2021

cupcakearmy added the help wanted Extra attention is needed label May 5, 2021

cupcakearmy closed this as completed Nov 11, 2021

cupcakearmy reopened this Dec 23, 2021

cupcakearmy closed this as completed Jun 13, 2022

arm64 compatible docker #4

arm64 compatible docker #4

Comments

cyrrelsneer commented May 3, 2021

cupcakearmy commented May 3, 2021 • edited

cyrrelsneer commented May 4, 2021 • edited

cupcakearmy commented May 4, 2021 • edited

cyrrelsneer commented May 4, 2021

cupcakearmy commented May 4, 2021

cupcakearmy commented May 4, 2021

cyrrelsneer commented May 4, 2021

cupcakearmy commented May 4, 2021

cyrrelsneer commented May 4, 2021

cupcakearmy commented May 4, 2021

cupcakearmy commented May 4, 2021

cyrrelsneer commented May 4, 2021

cupcakearmy commented May 4, 2021

cyrrelsneer commented May 5, 2021

cupcakearmy commented May 5, 2021

ThisIsBenny commented May 16, 2021

cupcakearmy commented May 16, 2021

ThisIsBenny commented May 16, 2021

cupcakearmy commented May 19, 2021

cupcakearmy commented May 19, 2021

vladosam commented Dec 23, 2021

cupcakearmy commented Dec 23, 2021 • edited

cupcakearmy commented Dec 23, 2021

vladosam commented Dec 23, 2021

cupcakearmy commented Dec 23, 2021

cupcakearmy commented Dec 23, 2021

vladosam commented Dec 23, 2021

cupcakearmy commented Dec 23, 2021

vladosam commented Dec 23, 2021

cupcakearmy commented Dec 23, 2021

vladosam commented Dec 23, 2021

0xSh1v4 commented Dec 30, 2021

cupcakearmy commented Dec 30, 2021

vladosam commented Dec 30, 2021

0xSh1v4 commented Dec 30, 2021

cupcakearmy commented Dec 30, 2021

vladosam commented Dec 31, 2021

cupcakearmy commented Jan 3, 2022

0xSh1v4 commented Jan 3, 2022

cupcakearmy commented May 3, 2021 •

edited

cyrrelsneer commented May 4, 2021 •

edited

cupcakearmy commented May 4, 2021 •

edited

cupcakearmy commented Dec 23, 2021 •

edited