docker logs mbind: Operation not permitted

[coding-chenkaikai]

你好，执行docker run mysql:8.0.1的时候，docker logs 查看容器日志出现mbind: Operation not permitted，最初以为是权限的问题，添加--cap-add=ALL参数，还是会出现该日志，请问下该问题的影响范围是什么以及如何避免出现？

same issue here

[ltangvald]

The server use mbind for NUMA (non-uniform memory access) operations, but Docker blocks this access by default. It's possible to provide a custom profile that allows it, but the syntax of the profile files has changed across Docker versions, so it's kind of messy. There's more about this here: https://docs.docker.com/engine/security/seccomp/

[tianon]

Closing since this is more an issue with the default configuration of Docker's seccomp profile, and there's not anything we can do to fix this in the image itself.

See docker-library/mongo#113 for a similar issue over on the mongo image.

As noted there, adding something to the documentation (especially referencing the error message) would be a great idea. 👍

[johncmunson]

All of a sudden I started getting these mbind errors as well. For me, the solution was locking down the version of the mysql docker image. I changed my docker-compose.yml from...

services:
  mysqldb:
    image: mysql

to...

services:
  mysqldb:
    image: mysql:5.7.22

[atkinchris]

@johncmunson - we're seeing the same thing - mbind: Operation not permitted with no other environment changes in the last few days, when running Docker on an EC2.

[nirodg]

None of this workarounds does work for me. I've tried on my local env, on a virtual machine and even on a VPS and nothing, same issue. I've tried using a different version and it crashes, seriously thinking it might be a bug or something.

version: '3.1'
services:
  mysql:
    image: mysql
    container_name: mysql.dev
    restart: always
    ports:
     - 13306:3306
    environment:
      MYSQL_ROOT_PASSWORD: brage
      MYSQL_DATABASE: mysqlapp

  adminer:
    image: adminer
    restart: always
    links:
      - mysql
    ports:
      - 18080:8080

The only way to connect is by docker exec -it mysql.dev mysql -u root -p

To connect to adminer it´s straightforward, just open the browser and type http://localhost:18080

[yosifkit]

@nirodg, your issue is unrelated to mbind. The mbind error does not cause MySQL to fail to run or refuse connections. Assuming that your adminer is unable to connect to MySQL, then most likely you are running into #409, #419, #424.

[skjnldsv]

Please bump when latest tag images are fixed :/

[tianon]

The mbind error is a red herring; it shouldn't stop the server from working. Whatever issue you're experiencing is likely deeper than just mbind.

[samabsalom]

I came across this by googling the mbind thing. Just adding this here to allow others to know that regardless of the root issue using 5.7 instead of latest fixed the problem and got the container running again
Thanks all!