You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Environments: Fix jobs, WordPress.tv and Support Forums envs failing to start - #1205
Docker Desktop's runc (1.3.5) won't create a single-file mountpoint inside the core directory wp-env bind-mounts:
error mounting ".../mocks/mu-plugins/wporg-dev-login.php" to rootfs at "/var/www/html/wp-content/mu-plugins/wporg-dev-login.php": ... mountpoint ".../wordpress-latest/wp-content/mu-plugins/wporg-dev-login.php" is outside of rootfs
wp-env re-extracts the nightly core zip whenever the config changes, so the mountpoint never exists ahead of time and start fails every time. Directory mountpoints are unaffected. This hits every env that maps a single file: jobs, WordPress.tv and Support Forums.
This maps only directories:
jobs and WordPress.tv: their own mu-plugins move into jobs/mu-plugins/ and wordpress-tv/mu-plugins/, mapped as wp-content/mu-plugins. The shared dev login helper stays in mocks/mu-plugins/ (the other envs map that whole directory), reached through a mapped wp-content/env-mocks and a one-line loader.
Support Forums: wporg-ratings.php moves into plugins/wporg-ratings/, mapped as a directory.
Testing
npm run wptv:env start: starts after a fresh core extraction; dev-login.php and wptv-local.php load, and the login screen shows the dev login button.
npm run jobs:env start: dev-login.php, jetpack-offline-subscriptions.php and jobs-open-to-work.php load.
npm run support:env start: starts; wporg-ratings is active on the plugins and themes sites.
Docker Desktop's runc (1.3.5) refuses to create a single-file mountpoint inside the core directory wp-env bind-mounts, failing with "mountpoint ... is outside of rootfs". wp-env re-extracts the nightly core zip whenever the config changes, so the jobs, WordPress.tv and Support Forums environments couldn't start.
Map directories instead: each environment's own mu-plugins move into a per-environment mu-plugins directory, the shared dev login helper is reached through a mapped mocks directory, and the local wporg-ratings plugin gets its own directory.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No actionable comments were generated in the recent review.
Walkthrough
Jobs and WordPress.tv now mount MU-plugin directories and shared mocks, and add loaders for the shared development login helper. Support-forums now maps the wporg-ratings plugin directory. The README updates the WordPress.tv configuration path.
Jobs and WordPress.tv map their MU-plugin directories and wp-content/env-mocks to local directories. Each environment adds a loader for the shared development login helper. The README updates the WordPress.tv configuration path.
WordPress/wordpress.org#1202: Adds the WordPress.tv environment with single-file MU-plugin mappings that this change replaces.
WordPress/wordpress.org#1075: Adds Jobs environment mock mappings that this change replaces with a directory mount.
Merge Risk: Minimal · up to 2bc6e
The directory mappings preserve the expected plugin paths. No merge-blocking issue was identified.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly describes the startup fixes for the three affected environments.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 3 files. (4 skipped: 4 unsupported.)
Finishing Touches
Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Tip
🎯 Customize your risk assessments
Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.
✅ Automatic approvals, with your rules
Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docker Desktop's runc (1.3.5) won't create a single-file mountpoint inside the core directory wp-env bind-mounts:
wp-env re-extracts the nightly core zip whenever the config changes, so the mountpoint never exists ahead of time and
startfails every time. Directory mountpoints are unaffected. This hits every env that maps a single file: jobs, WordPress.tv and Support Forums.This maps only directories:
jobs/mu-plugins/andwordpress-tv/mu-plugins/, mapped aswp-content/mu-plugins. The shared dev login helper stays inmocks/mu-plugins/(the other envs map that whole directory), reached through a mappedwp-content/env-mocksand a one-line loader.wporg-ratings.phpmoves intoplugins/wporg-ratings/, mapped as a directory.Testing
npm run wptv:env start: starts after a fresh core extraction;dev-login.phpandwptv-local.phpload, and the login screen shows the dev login button.npm run jobs:env start:dev-login.php,jetpack-offline-subscriptions.phpandjobs-open-to-work.phpload.npm run support:env start: starts;wporg-ratingsis active on the plugins and themes sites.🤖 Generated with Claude Code
Summary by CodeRabbit