Repository navigation
Fix CI Chrome launch and keep production always on - #67
Merged
Merged
Conversation
The setup-chrome action installs Chrome into the tool cache without an
AppArmor profile, so on ubuntu-24.04 Chrome can't create its sandbox and
fails to launch ("No usable sandbox!"). The preinstalled Google Chrome
and ChromeDriver on the runner image don't have this problem.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pin launch-cart to ord alongside its database, and disable auto-stop so production machines never go to sleep. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dev app isn't used, so stop deploying to launch-cart-dev. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
Both Fly apps (
launch-cart,launch-cart-dev) are suspended with no machines, so nothing is serving requests. Recent commits never deployed because CI has failed on every push since the Nov 8 upgrade, and the deploy job depends on the test job.The CI failure was Chrome not starting at all ("No usable sandbox!"). The upgrade moved CI to
ubuntu-24.04and addedbrowser-actions/setup-chrome. That action installs Chrome into the tool cache without an AppArmor profile. Ubuntu 24.04 restricts unprivileged user namespaces through AppArmor, so that copy of Chrome can't create its sandbox.Changes
setup-chromeand use the Google Chrome and ChromeDriver preinstalled on the runner image (/usr/bin/google-chrome,$CHROMEWEBDRIVER/chromedriver).launch-cart-devdeploy step is removed because that app is unused.fly.toml: setprimary_region = "ord"so prod runs in the same region aslaunch-cart-db. Setauto_stop_machines = "off"andmin_machines_running = 1so production never goes to sleep.Verification
fly config validatepasses for both configs.Note
Merging deploys current
mainto production (launch-cart). That includes the Elixir 1.20.5 / LiveView 1.2.13 upgrade and the reply-to change, which have not run in production yet.🤖 Generated with Claude Code