The Ultimate Guide to High Availability with MariaDB

Comments - Problem starting up docker for the first time.

2 years ago Daniel Black
Re: Problem starting up docker for the first time. [Answer]

This looks like the problem we where seeing in our infra MDBF-357. The common bit is the -x "$dirname0/@bindir@/my_print_defaults" part of my_print_defaults failing the same way.

In short the docker version you are using in the (end of life) squeeze is filtering out the faccess2 system call that bash is using to test the presence of my_print_defaults.

--security-opt seccomp=unconfined might help with your current version, but a better solution is upgrading squeeze and the OCI container runtime that comes with it.

I also recommend podman instead of docker. The command line options are the same. . Debian unstable versions have podman-docker. I have a docker -> podman symlink for the tools/scripts that use docker.

 
2 years ago Oleg Home
Re: Problem starting up docker for the first time.

Thank you Daniel for a detailed explanation! --security-opt seccomp=unconfined resolved it for me and I think I will stick with it for some time as I have many containers running on nas and this one is just a part of "emoncms" that I am testing. I will look at "podman" and other nas distros when I am ready to upgrade. Thank you, Oleg

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.