-
Notifications
You must be signed in to change notification settings - Fork 279
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
[Bug]: docker install MO 0.8.0 failed #10593
Comments
with --privileged=true it is able to run now.
|
related with: docker-library/golang#467 the best option maybe disable CGO. also can be fixed by use --priviledge option, we need add document to explain this before CGO is disabled |
This comment was marked as off-topic.
This comment was marked as off-topic.
in progress |
will check this issuer in next week |
sorry for delay, will check it in next few days |
I am working on it now |
I cannot reproduce this issue on following env(I use a VMware virtual machine):
I install docker following steps here: https://docs.docker.com/engine/install/centos/#install-using-the-repository
do I miss some points to reproduce this issue @dengn |
I can reproduce this issue in tencent cloud centos machine with docker 1.13.1, but after I upgrade docker version to community version 24.0.5, MO can start normally. It is very likely that the inherited docker 1.13.1 is too old. centos kernel version: 3.10.0-1160.88.1.el7.x86_64 |
After communicating with person who open original issue, it turns out that the cause of this issue is version of docker client and docker server mismatched: the docker client version is 24.0.4 while the server version is 20.10.9. after upgrade docker server to 24.0.4 the probelm is solved. The reason behind this maybe the 24.0.4 client may enable more default seccomp option while server not default allowed. we may need to determine a porper docker version scope for our user. |
The root cause is go 1.20.0 introduce a new syscall which will blocked by the default seccompl profile in older versions of docker engine. The problem has been fixed in moby/moby#43594, the fix is available in docker 23.x or 24.x version and has been back-ported to We need to update the documentation to notice people that they should and |
documents need update |
@dengn hi, should this issue be closed ? since there is another issue tracing document enhancement |
Is there an existing issue for the same bug?
Environment
Actual Behavior
original issue: matrixorigin/matrixorigin.io.cn#508
I've also recreated this issue in a centos 7.9 and docker version 1.13. The developer who fired this issue used docker version 24.0.4.
But this docker problem doesn't happen in debian 11.1 and macOS.
It seems to be a permission related issue.
Expected Behavior
No response
Steps to Reproduce
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: