-
-
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
[🚀 Feature]: Decreasing container layers #2210
Comments
@efeozsoy, 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! |
Several |
This issue is looking for contributors. Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested. |
If without private info, can you share a sample that you are doing for testing purposes during development? |
we are using codebuild to push to ecr but for example you can make a simple automation project to inject it, also we are downloading python to run automation.
it is smth like that i created via chatgpt since i can not provide original codes |
Ok, that's fine, I also found a command to count the number of layers
Just update something and check this number can be decreased |
Below is the image layers count after changing. It will be released in 4.20.0 docker history selenium/base:trunk-20240423 -q | wc -l
29
docker history selenium/hub:trunk-20240423 -q | wc -l
41
docker history selenium/distributor:trunk-20240423 -q | wc -l
38
docker history selenium/router:trunk-20240423 -q | wc -l
37
docker history selenium/sessions:trunk-20240423 -q | wc -l
35
docker history selenium/session-queue:trunk-20240423 -q | wc -l
37
docker history selenium/event-bus:trunk-20240423 -q | wc -l
37
docker history selenium/node-base:trunk-20240423 -q | wc -l
45
docker history selenium/node-chrome:trunk-20240423 -q | wc -l
61
docker history selenium/node-edge:trunk-20240423 -q | wc -l
61
docker history selenium/node-firefox:trunk-20240423 -q | wc -l
58
docker history selenium/node-docker:trunk-20240423 -q | wc -l
37
docker history selenium/standalone-chrome:trunk-20240423 -q | wc -l
72
docker history selenium/standalone-edge:trunk-20240423 -q | wc -l
72
docker history selenium/standalone-firefox:trunk-20240423 -q | wc -l
69
docker history selenium/standalone-docker:trunk-20240423 -q | wc -l
45
docker history selenium/video:ffmpeg-7.0-20240423 -q | wc -l
53 |
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. |
Feature and motivation
In our current structure we had to use docker standalone image and latest version has 126 layers which has blocking us to add new things inside the container and taking a docker and push to aws ecr. It gives "rpc error: code = Unknown desc = failed to register layer: max depth exceeded what does it mean"
Usage example
we are currently planning to add other packages and even automation project inside this image but it blocks to proceed without changing the original project.
The text was updated successfully, but these errors were encountered: