CALL FOR HELP: New Builds Broken due to Ubuntu 20+ build failures.
I have had to keep CI and local builds running on 18.04 because anything higher just won't build. Installing any service, Mysql, apache, in Docker builds with a base image higher than ubuntu 18 always fails, locally and in github CI with:
Service is in unknown state
Maybe it's something to do with https://github.com/geerlingguy/drupal-vm/issues/2156 or https://github.com/geerlingguy/drupal-vm/issues/2090
Things were ok, because we could still build on Ubuntu18... Until April rolled around.
Now, Ubuntu 18 is EOL. Which means, PHP Packages no longer exist. Which means...
All docker builds are failing.
I have spent so much time struggling with these things it has destroyed the project.
We are at a standstill. Can anyone help?
Here is the latest failure: https://github.com/opendevshop/devshop/actions/runs/5534546712/jobs/10099651001#step:9:2662
Same thing, locally and in Github CI:
#17 69.99 Ensure MySQL is stopped after initial install....
#17 70.57 localhost failed | msg: Service is in unknown state
#17 70.58
I haven't encountered that issue in my Docker Ansible role still running on 18.04, but I'm wondering—if these tests are run in Docker containers, have you set cgroupns mode to host, and set the cgroup volume to rw? https://github.com/geerlingguy/ansible-role-docker/blob/master/molecule/default/molecule.yml#L11-L13
Sorry, my post is poorly written.
The 18.04 containers are the ONLY ones that build. Anything higher causes service installation to fail on Docker Build, not run.
Do those settings affect build runs?
@geerlingguy I think it's the same thing that was happening here: https://github.com/geerlingguy/drupal-vm/issues/2090
Even if I drop out postfix, apache (or any other service) does the same thing:
@jonpugh I have some interest in investigating this stuff, I'd like to see the project working (selfishly so I can mess around with it and maybe run some Drupal sites, but also as an available alternative for orgs it would be a fit for). I am 100% new to the codebase though, is https://docs.opendevshop.com/developing-devshop/developing-devshop the current recommended dev setup? I can't make any promises of efficacy, but I'd like to get in, poke around, tinker with things, and see if by chance/luck, I can fix any issues.
The last few time I tried to spin up a digital ocean droplet and try this out, it failed for me and I assume for the reason outlined here as I was on a newer Ubuntu version. Anyhow, no promises of results as I said, but I just want to confirm the docs above are the best route to tinkering, thanks!
I never got that issue resolved in the Drupal VM image build :(
It was a weird issue that would probably require a lot more debug work—and I believe was only reproducing in the GitHub Actions environments, which made it even harder to debug.
@dustinleblanc I have been using the robo/up command successfully from 1.x branch. Let me know how it goes?
@geerlingguy thanks for chiming in. I've pretty much given up at this point. Local builds work again, and tests pass using the old containers, so ...
🤷🏻
First time I installed on 22.04 with 1.8.0-beta3, I was not getting mysql started properly, as above.
Next issue, I was getting php 7.4 -- I was able to edit the /var/aegir/devshop-control/vars.yml and add php_version: "8.1" and run devshop-ansible-playbook to get to PHP 8.1.