docker-selenium/4.35.0.20250828 package update

[octo-sts]

[octo-sts]

📦 Build Failed: Missing Dependency

install: can't stat 'generate_config': No such file or directory

Build Details

Category	Details
Build System	melange
Failure Point	install -Dm755 generate_config /home/build/melange-out/docker-selenium-standalone/opt/bin/

Root Cause Analysis 🔍

The build process is trying to install a file named 'generate_config' but this file does not exist in the expected location. This is likely a missing file that should have been created earlier in the build process or is missing from the source package.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Suggested Changes

File: docker-selenium.yaml

• removal at line line ~515 (docker-selenium-standalone subpackage pipeline)
  Original:

install -Dm755 generate_config ${{targets.contextdir}}/opt/bin/

Content:

Remove the installation of generate_config file that doesn't exist

Click to expand fix analysis

Analysis

No similar build failures were provided for analysis. The current build failure indicates that the 'generate_config' file is missing during the installation step for the docker-selenium-standalone subpackage. This appears to be a missing file issue where the build process expects a file that either doesn't exist in the source repository or wasn't created during the build process.

Click to expand fix explanation

Explanation

The build failure occurs because the build process is trying to install a file named 'generate_config' from the Standalone directory, but this file does not exist. Looking at the upstream Docker Selenium repository structure and the changelog, there's no indication that this file should exist in the Standalone directory. The NodeBase subpackage successfully installs generate_config, suggesting it exists there but not in Standalone. Since the standalone functionality likely doesn't require this specific configuration generation script (as it's a self-contained setup), removing this installation step should resolve the build failure without affecting functionality.

Click to expand alternative approaches

Alternative Approaches

• Copy generate_config from NodeBase directory if standalone needs configuration generation capabilities
• Create a conditional installation that only installs generate_config if the file exists
• Investigate if generate_config should be generated during the build process rather than installed from source

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.

[dnegreira]

I was looking into this to see if we could remediate a CVE by bumping to the new version.

generate_config doesn't exist anymore in Standalone.

Single Node/Standalone Image With All Browsers

From image tag 4.35.0 onwards, a single Node/Standalone image is available with all browsers are pre-installed. Those images are selenium/standalone-all-browsers (standalone all in one), selenium/node-all-browsers (for Hub-Node mode).

SeleniumHQ/docker-selenium#2942