-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: Out of memory errors in hub #2014
Comments
@krimsonkla, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
@krimsonkla do you know what the fix is? I did not see an obvious fix after reading the issues. |
Same issue i 'm facing as well after pulling latest images for hub and nodes. For hub i did upgrade OS to jammy on the VM i'm running and can verify it worked. As i have lot of VMs i decided to pull older images with ubuntu 20. Will verify upgrading the docker engine as well on older ubuntu OS. |
I have read on this thread https://stackoverflow.com/a/72841934/14532601 |
Ubuntu 16.04.2 LTS Verified now , no issue seen for version 20.10.7 Instead of upgrading docker engine i'm going to upgrade all our VMs to jammy though as we have been sitting on older version anyways (16/18 LTS) |
@diemol I couldn't find a fix. I had to pin back to the pre jammy images. I spent several hours scouring the net and trying different fixes, none of which helped. |
@krimsonkla what about the above comment from @VietND96? |
I am having the same issue as everyone else here: OS: CentOS Linux 7 |
I am also getting same memory error I was using docker $ docker -v
Docker version 20.10.7, build f0df350
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" |
Seems that an upgrade to latest docker and if you are using Ubuntu then a bump to Jammy is needed. |
I upgraded the version to 20.10.10 and the problem was solved |
Thank you for letting us know. I will close this issue, upgrading solves it. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
After updating to the latest hub, we started receiving out-of-memory errors on the hub. Attempted setting SE_JAVA_OPTS and seccomp=unconfined. Neither of which helped. After some searching, I found this is a common and recent issue with docker on jammy as reported in the following repositories.
adoptium/temurin-build#2974
adoptium/containers#215
Docker Selenium recently updated to Jammy here: #1923
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
Ubuntu 16.04.7 LTS
Docker Selenium version (tag)
20.10.7, build f0df350
The text was updated successfully, but these errors were encountered: