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

Can This Server Run Milvus Docker CPU Version? #7989

Closed
PeteWorkspaces opened this issue Sep 15, 2021 · 4 comments
Closed

Can This Server Run Milvus Docker CPU Version? #7989

PeteWorkspaces opened this issue Sep 15, 2021 · 4 comments
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days
Milestone

Comments

@PeteWorkspaces
Copy link

PeteWorkspaces commented Sep 15, 2021

Can not run Milvus CPU Version。

On My Test Server,I've Try to Run Docker18.03+Milvus0.8,But it does not work。Docker Logs something as below:
./start_server.sh: line 3: 8 Illegal instruction (core dumped) ../bin/milvus_server -c ../conf/server_config.yaml -l ../conf/log_config.conf

And I've Change to Run Docker19.03+Milvus1.1.1,But it Still does not work,Docker Logs nothing error!。

Only logs when I try to use 'Docker run':
INFO[2021-09-15T16:29:22.909002284+08:00] shim containerd-shim started address="unix:///run/containerd/s/77303fcf31c30c2edee770727729aa3b5bd36fc9bf81ebafd24e2f31cbac5156" debug=false pid=4340
[root@]# INFO[2021-09-15T16:29:23.251535808+08:00] shim reaped id=ba6e2376e9c6f73e8316eac9350c5e0d588906336ce736578d4465c4c803863a
INFO[2021-09-15T16:29:23.261122500+08:00] ignoring event module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"

Environment:

  • Milvus 1.1.1
  • OS(Ubuntu or CentOS): Red Hat Enterprise Linux Server release 7.6 (Maipo)
  • CPU/Memory: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni ssse3 cx16 pcid sse4_2 x2apic hypervisor lahf_lm
  • GPU: 无
  • Others:

Configuration file:

no change

Additional context:

no change

@PeteWorkspaces PeteWorkspaces added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 15, 2021
@xiaofan-luan
Copy link
Contributor

please change the issue into english~ thanks, that may helps other people in the community

@yhmo yhmo added this to the 1.x milestone Sep 17, 2021
@yhmo
Copy link
Contributor

yhmo commented Sep 17, 2021

Typically, "Illegal instruction" error is caused by incompatible hardware. Most of x86 cpu with SSE4.2, AVX, AVX2, AVX512 instruction can run milvus.

From your description, your cpu supports sse4_2, theoretically it can meet the requirement. Is it inter cpu?

I notice the error "shim reaped", it is related to docker. I am not sure how to solve this, you can refer this page:
containerd/containerd#2202

@yhmo yhmo self-assigned this Sep 17, 2021
@stale
Copy link

stale bot commented Oct 17, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added stale indicates no udpates for 30 days and removed stale indicates no udpates for 30 days labels Oct 17, 2021
@stale
Copy link

stale bot commented Nov 17, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Nov 17, 2021
@stale stale bot closed this as completed Nov 24, 2021
@PeteWorkspaces PeteWorkspaces changed the title 请问这个服务器配置是不是不能运行Milvus Docker CPU版本? Can This Server Run Milvus Docker CPU Version? Nov 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days
Projects
None yet
Development

No branches or pull requests

3 participants