Closed mdelapenya closed 1 month ago
mtojek
commented
3 years ago It looks like the application was built properly, but there is problem with a single container:
Container "b4322208e286" is unhealthyIt would be nice to look what's inside, maybe logs contain something. This might be also a problem if the stack is booted on machine with low resource limits (memory), so it can't boot up in time (hence unhealthy).
mtojek
commented
3 years ago @mdelapenya If you look at the Releases page, it includes ARM support (64bit): https://github.com/elastic/elastic-package/releases .
Could you please retry your scenario to revalidate this issue?
marclop
commented
3 years ago I ran into this while trying to test the apm-server with docker-compose up -d in the `apm-server repo https://github.com/elastic/apm-server/pull/6177#issuecomment-920222496.
mtojek
commented
3 years ago I assume you're referring to signal 11 (Segmentation fault) - core dumped. I'm not sure if this is related to the problem mentioned here.
Are you sure that it isn't related to qemu?
marclop
commented
3 years ago @mtojek that's coming from inside the container which failed to start which uses the docker.elastic.co/package-registry/distribution:snapshot docker image. We use docker-compose in the APM server team, you can see the docker-compose.yml file here.
$ CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4d9948f77f82 f32cf92344d6 "/entrypoint.sh" 33 minutes ago Up 33 minutes (unhealthy) 0.0.0.0:51432->8080/tcp apm-server_package-registry_1
$ docker logs -n10 apm-server_package-registry_1
2021/09/16 11:16:43 zookeeper 1.0.0 /packages/snapshot/zookeeper/1.0.0
2021/09/16 11:16:43 zoom 0.5.0 /packages/snapshot/zoom/0.5.0
2021/09/16 11:16:43 zoom 0.5.1 /packages/snapshot/zoom/0.5.1
2021/09/16 11:16:43 zscaler 0.3.0 /packages/snapshot/zscaler/0.3.0
2021/09/16 11:16:43 zscaler 0.3.1 /packages/snapshot/zscaler/0.3.1
2021/09/16 11:16:43 zscaler 0.3.2 /packages/snapshot/zscaler/0.3.2
2021/09/16 11:16:43 zscaler 0.3.3 /packages/snapshot/zscaler/0.3.3
2021/09/16 11:16:43 Packages in /packages/local:
2021/09/16 11:16:43 apm 0.5.0 /packages/local/apm/0.5.0
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
$ uname -a
Darwin REDACTED 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101 arm64The problem here comes not that the elastic-package isn't being cross compiled for linux/darwin arm64, but that the docker images aren't being built and published for arm64:
$ docker inspect --format='OS: {{ .Os }}, Arch: {{ .Architecture }}' docker.elastic.co/package-registry/distribution:snapshot
OS: linux, Arch: amd64Ideally, we'd also build the docker images for multiple architectures instead of only for amd64.
mtojek
commented
3 years ago @jlind23 I think we need a meta-issue to support ARM arch in our developer pipeline (https://github.com/elastic/package-registry/issues/723 and https://github.com/elastic/elastic-package/issues/497 can be linked there.)
jlind23
commented
3 years ago Just created it here: https://github.com/elastic/elastic-package/issues/539
mrodm
commented
1 month ago The problem here comes not that the elastic-package isn't being cross compiled for linux/darwin arm64, but that the docker images aren't being built and published for arm64: $ docker inspect --format='OS: {{ .Os }}, Arch: {{ .Architecture }}' docker.elastic.co/package-registry/distribution:snapshot OS: linux, Arch: amd64 Ideally, we'd also build the docker images for multiple architectures instead of only for amd64.
Closing this issue since the support for Package-Registry container images as a multi-platform one (linux/amd64 and linux/arm64) was added in https://github.com/elastic/package-registry/pull/1162 and those docker images are already used in the Elastic stack started by elastic-package.
We are trying to consume the tool directly in the e2e-testing framework, to simplify/unify the provisioning part of the runtime dependencies, but when executed "stack up" on ARM workers on CI, we see this error:
I wonder if the compose implementation is requesting the right platform for all components in the stack.