-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Cannot build new mysql 5.7 container #950
Comments
Something as simple as running just docker run mysql:5.7 creates the error. I cannot wait, so unforturnelty i have to reinstall my system as i cannot wait for the issue to be solved. |
A shot in the dark, but sounds like a duplicate of #579; perhaps setting some ulimits would work?
|
Unfortunately, we do not have the bandwidth to provide in-depth integration/deployment/environment debugging or support here; these sorts of questions/requests would be more appropriately posted to a dedicated support forum, such as the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow. |
So i have to run a container with a mysql 5.7 database. But whenever i try to start it, it fills both my memory and my swp file within seconds until the kernel kills it.
It is not an issue with the 8 version but it is not possible for me to upgrade to that for the time being.
When trying to run or build the continer in docker-compose up i get the following error:
and the journalctl gives the following error:
the docker-compose.yml file to replicate:
I have tried uninstalling both docker-compose and docker, removed all my containers, cleared all caches, build without cache and pruned all containers in docker.
I am using Docker version 23.0.1
Docker Compose version 2.16.0
and
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=22.0.4
DISTRIB_CODENAME=Sikaris
DISTRIB_DESCRIPTION="Manjaro Linux"
The above information is every error i have been able to find related to the problem.
This bug is making it almost impossible to do my job, so i hope someone can help me to get it to work.
The text was updated successfully, but these errors were encountered: