Ewoud Kohl van Wijngaarden

As noted in a meeting, the failure may be due to nulldb: https://github.com/theforeman/foreman/blob/17f6c0368e88104df01c3fc68478561ec2861524/.github/workflows/foreman.yml#L73

I suppose we need VMs for proper kernel facts that containers wouldn't get right

No, I started to do that but it's the first time I used obal in a long time and immediately ran into https://github.com/theforeman/obsah/pull/37 again. It's https://www.youtube.com/watch?v=AbSehcT19u0 all over again.

> requires [theforeman/foreman-tasks#752](https://github.com/theforeman/foreman-tasks/pull/752) We support `gemfile.d` where you can add the foreman-tasks dependency with your branch: https://github.com/theforeman/actions/blob/61c576caf6aea7bf18178a2bac7b21178fb44ed9/.github/workflows/foreman_plugin.yml#L121-L123

@evgeni this failed to build and has already been rotated, but I'm assumed it failed to build because it needs a patched Foreman and/or foreman-tasks. I recall you did something...

Ah yes. Looks like I'll manually compose a repository with all packages. Then it's also an easy place to test everything.

> `61.42: Exec[foreman-rake-db:migrate]` This runs `foreman-rake` twice, plus some other code. > 38.11: Service[foreman] > 26.33: Service[dynflow-sidekiq@worker-hosts-queue-1] > 26.27: Service[dynflow-sidekiq@worker-1] > 25.94: Exec[foreman-rake-db:seed] > 25.57: Service[dynflow-sidekiq@orchestrator] This all also loads...

Note that https://github.com/Shopify/bootsnap says it can work in production: > All Bootsnap features are enabled in development, test, production, and all other environments according to the configuration in the setup....

That's nice win IMHO. They do mention the cache directory isn't cleaned so let's discuss strategies for that. If it's stored in `/run` then it's probably fine, but I don't...

In #3534 I made a start