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 deployment on arm architecture #1973

Closed
a986837717 opened this issue Mar 1, 2024 · 14 comments
Closed

docker deployment on arm architecture #1973

a986837717 opened this issue Mar 1, 2024 · 14 comments
Labels
bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@a986837717
Copy link

What happened?

docker-compose up -d启动后zk启动失败报错,openim-server容器unhealthy,使用的cpu是鲲鹏920
server容器报错:

Check all dependent service ports

Check OpenIM service name

!!! [0301 17:56:40] Call tree:
!!! [0301 17:56:40] 1: /openim/openim-server/scripts/install/openim-msgtransfer.sh:152 openim::msgtransfer::check(...)
!!! [0301 17:56:40] 2: /openim/openim-server/scripts/check-all.sh:84 source(...)
!!! Error in /openim/openim-server/scripts/install/openim-msgtransfer.sh:66
Error in /openim/openim-server/scripts/install/openim-msgtransfer.sh:66. 'PIDS=$(pgrep -f "${OPENIM_OUTPUT_HOSTBIN}/openim-msgtransfer")' exited with status 1
Call stack:
1: /openim/openim-server/scripts/install/openim-msgtransfer.sh:66 openim::msgtransfer::check(...)
2: /openim/openim-server/scripts/install/openim-msgtransfer.sh:152 source(...)
3: /openim/openim-server/scripts/check-all.sh:84 main(...)
Exiting with status 1

Begin to check all openim service

+++ [0301 17:58:41] Check all dependent service ports

Check all dependent service ports

Check OpenIM service name

!!! [0301 17:58:41] Call tree:
!!! [0301 17:58:41] 1: /openim/openim-server/scripts/install/openim-msgtransfer.sh:152 openim::msgtransfer::check(...)
!!! [0301 17:58:41] 2: /openim/openim-server/scripts/check-all.sh:84 source(...)
!!! Error in /openim/openim-server/scripts/install/openim-msgtransfer.sh:66
Error in /openim/openim-server/scripts/install/openim-msgtransfer.sh:66. 'PIDS=$(pgrep -f "${OPENIM_OUTPUT_HOSTBIN}/openim-msgtransfer")' exited with status 1
Call stack:
1: /openim/openim-server/scripts/install/openim-msgtransfer.sh:66 openim::msgtransfer::check(...)
2: /openim/openim-server/scripts/install/openim-msgtransfer.sh:152 source(...)
3: /openim/openim-server/scripts/check-all.sh:84 main(...)
Exiting with status 1

zk容器报错:
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error

What did you expect to happen?

启动server失败

How can we reproduce it (as minimally and precisely as possible)?

根据https://docs.openim.io/zh-Hans/guides/gettingStarted/dockerCompose部署执行docker up -d

Anything else we need to know?

No response

version

1060a

Cloud provider

OS version

UOS操作系统1060a版arm架构

Install tools

@a986837717 a986837717 added the bug Categorizes issue or PR as related to a bug. label Mar 1, 2024
@kubbot kubbot changed the title arm架构上docker部署 docker deployment on arm architecture Mar 1, 2024
@kubbot
Copy link
Contributor

kubbot commented Mar 1, 2024

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@a986837717
Copy link
Author

上面的信息就是报错日志

@kubbot
Copy link
Contributor

kubbot commented Mar 4, 2024

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


The above information is the error log

@cubxxw
Copy link
Contributor

cubxxw commented Mar 4, 2024

I'm afraid the zookeeper container image may not be compatible with this architecture.

  zookeeper:
    image: bitnami/zookeeper:${ZOOKEEPER_IMAGE_VERSION:-3.8}
    container_name: zookeeper
    ports:
     - "${ZOOKEEPER_PORT:-12181}:2181"
    volumes:
      - "/etc/localtime:/etc/localtime"
    environment:
      - ALLOW_ANONYMOUS_LOGIN=yes
      - TZ="Asia/Shanghai"
    restart: always
    networks:
      server:
        ipv4_address: ${ZOOKEEPER_NETWORK_ADDRESS:-172.28.0.5}

If possible, could you please consider using a more suitable mirror, or specifying the architecture as amd64 in the docker compose? Thank you!

@a986837717
Copy link
Author

如何更换镜像呢,我是用的飞腾D2000的arm架构,如果修改docker-compose中的架构为AMD64恐怕会导致其他报错吧

@kubbot
Copy link
Contributor

kubbot commented Mar 4, 2024

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


How to change the image? I am using the arm architecture of Feiteng D2000. If I modify the architecture in docker-compose to AMD64, I am afraid it will cause other errors.

@a986837717
Copy link
Author

我是直接通过官方给的包和安装步骤进行的

@kubbot
Copy link
Contributor

kubbot commented Mar 4, 2024

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


I did it directly through the official package and installation steps.

@cubxxw
Copy link
Contributor

cubxxw commented Mar 4, 2024

如何更换镜像呢,我是用的飞腾D2000的arm架构,如果修改docker-compose中的架构为AMD64恐怕会导致其他报错吧

可以试试的,可以问问 chatgpt ,我相信很好解决

换镜像可以去 https://hub.docker.com/ 找找

@kubbot
Copy link
Contributor

kubbot commented Mar 4, 2024

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


How to change the image? I am using the arm architecture of Feiteng D2000. If I modify the architecture in docker-compose to AMD64, I am afraid it will cause other errors.

You can try it, you can ask chatgpt, I believe it can be solved easily

To change the image, you can go to https://hub.docker.com/ to find it.

@a986837717
Copy link
Author

请问咱们这项目有部署在arm架构的先例吗,有没有文档我借鉴一下,

@kubbot
Copy link
Contributor

kubbot commented Mar 4, 2024

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Is there any precedent for our project to be deployed on the arm architecture? Is there any document for reference?

@kubbot
Copy link
Contributor

kubbot commented May 4, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 4, 2024
@skiffer-git
Copy link
Member

deploying OpenIM is smoothy in release-v3.8 version, I recommend you update to this version, if you encounter new issue, please reopen this issue or open new issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants