We have a few sites at Acquia, and the host OS for those environments is Ubuntu 16 (which is based on Debian 9), running kernel 4.4.0-1133-aws.
However, the Lando Acquia recipe uses Debian 10, kernel 4.15.0-142-generic as the host OS.
It seems that a Lando Acquia recipe should use the same base OS that's used at Acquia to get the localdev environment as close to the production environment as possible.
Context:
Acquia doesn't officially support adding non-Drupal php libraries or extensions, but they will enable customer-compiled libraries / extensions. https://docs.acquia.com/cloud-platform/develop/non-drupal/
I'm looking at doing this, but I don't like the idea of compiling for two different OSes, or running different software in localdev than in production.
We have a few sites at Acquia, and the host OS for those environments is Ubuntu 16 (which is based on Debian 9), running kernel 4.4.0-1133-aws.
However, the Lando Acquia recipe uses Debian 10, kernel 4.15.0-142-generic as the host OS.
It seems that a Lando Acquia recipe should use the same base OS that's used at Acquia to get the localdev environment as close to the production environment as possible.
Context:
Acquia doesn't officially support adding non-Drupal php libraries or extensions, but they will enable customer-compiled libraries / extensions. https://docs.acquia.com/cloud-platform/develop/non-drupal/
I'm looking at doing this, but I don't like the idea of compiling for two different OSes, or running different software in localdev than in production.