Update Docker Image to Ubuntu 24.04 ( Noble ) #2739

pentatonicfunk · 2024-10-20T02:25:22Z

Update docker image to use Ubuntu 24.04 ( noble )
-- Add missing noble repository list
-- Hacky fix of pip shyaml install on Ubuntu 24.04: see https://pimylifeup.com/python-externally-managed-environment/
Update mariadb repo to OVH ( only on focal and noble ): see unable to provision using several providers on Arm64/Apple Silicon M3 chip #2727 (comment)
Introduce vvv_get_mysql_service_name, in attempt to improve mariadb vs mysql service inconsistency
-- Unable to replicate the service name inconsistency, but it happened. ref: Slack #docker
Minor output copy fixes / improvements
Introduce customizable general.php_cli_version
-- It does have use case for me personally at least
-- Generally this provides user with better control of PHP CLI version rather than meddling / replicating vvv_restore_php_default to change PHP CLI version: https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org/blob/main/docs/en-US/adding-a-new-site/changing-php-version.md?plain=1#L83

Checks

I've updated the changelog.
I've tested this PR: Partially
This PR is for the develop branch not the stable branch.
This PR is complete and ready for review.

Note on testing:

Currently i only have linux host testing machine. I've tested with Docker provider, and it went okay, logs attached
Tried using Virtualbox, but it keeps timing out / error

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

If anyone can help testing it, please

Changelogs:

Please advise

- wildcard

…-Vagrants/develop v3.11 PR

…-Vagrants/develop 3.11.2 on stable

…-Vagrants/develop 3.12 stable

…-Vagrants/develop v3.1.2 stable

# Conflicts: # provision/core/git/provision.sh

…beta

- Add OVH url in hosts_to_test ( keep the mariadb.gb.ssimn.org )

- Better messages

update-docs · 2024-10-20T02:25:26Z

Thanks for opening this pull request! Make sure CHANGELOG.md gets updated with this change, additionally any docs that need updated can be found at https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org

GitHub
GitHub - Varying-Vagrant-Vagrants/varyingvagrantvagrants.org: The VVV docs and website
The VVV docs and website. Contribute to Varying-Vagrant-Vagrants/varyingvagrantvagrants.org development by creating an account on GitHub.

tomjn · 2024-10-20T11:13:30Z

@pentatonicfunk how much of this can we split into separate PRs? Upgrading Ubuntu isn't a small task but adding the sources could be done and released pretty quickly to simplfy merging. Likewise some of the other changes are useful and quick to test on their own.

I am mindful that upgrading Ubuntu the last time resulted in some weirdness that needed investigation.

Also, the service changes, I was thinking of changing how services are restarted to use a VVV specific function to insulate against service and systemctl since there's a lot of duplication going on

pentatonicfunk · 2024-10-20T12:22:43Z

i will try to cherry picks into separate branches next week.

config/default-config.yml

tomjn · 2024-10-20T15:15:30Z

Vagrantfile

@@ -480,7 +480,7 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|

  # Docker use image.
  config.vm.provider :docker do |d, override|
-    d.image = 'pentatonicfunk/vagrant-ubuntu-base-images:20.04'
+    d.image = 'pentatonicfunk/vagrant-ubuntu-base-images:24.04'


does this trigger a VM rebuild for exsting Ubuntu 22 instances that upgrade?

good question, i dont know. it would be vagrant territory, no ? the decision whether docker container need rebuild or not would be based on what vagrant flow will be issued. in any case better to test it, i'll try to test

main concerns is if vagrant would kick up a fuss about mismatching images or if it would discard the container ( and the database + data ) to create a new 24 container

so i tested this, this is how i tested it

use upstream/develop branch

Vagrantfile still using 20.04 image

do vagrant up --provision

verify ubuntu version via vagarant ssh

vagrant@vvv:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal

create new post in one.wordpress.test to verify DB okay

switch to origin/docker-provider

Vagrantfile now 24.4

do vagrant halt to stop docker

do vagrant reload --provision to trigger reprovision

verify ubuntu version via vagarant ssh, expecting the Ubuntu should stay in 20.04

Last login: Fri Nov 15 15:33:51 2024 from 172.17.0.1 vagrant@vvv:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal

verify whether DB not discarded ( post still exists )

i think this is what we expected, right ?

no complains on provisioner

container not discarded

DB not discarded

i think what we can do is, add somewhere in docs ( if we haven't), if user wants to upgrade their OS is by doing

db_backup

vagrant destroy

vagrant up --provision --> this step will trigger 24.04

db_restore

config/homebin/vagrant_provision

provision/core/mariadb/provision.sh

tomjn · 2024-10-20T15:18:11Z

provision/core/vvv/provision.sh

-    sudo pip3 install wheel
-    sudo pip3 install shyaml
+
+    local OSVERSION_NUMBER=$(lsb_release lsb_release -sr)


shellcheck will probably flag this and a few other things, it should be something like this:

Suggested change

local OSVERSION_NUMBER=$(lsb_release lsb_release -sr)

local OSVERSION_NUMBER

OSVERSION_NUMBER=$(lsb_release lsb_release -sr)

huh, this adjustments causing error for some reason

lsb_release: error: No arguments are permitted

https://github.com/Varying-Vagrant-Vagrants/VVV/actions/runs/11580749924/job/32239965581?pr=2739

reverted it to the original changes. the checks / linting seems to be fine: https://github.com/Varying-Vagrant-Vagrants/VVV/actions/runs/11581054132/job/32240928199?pr=2739
and we already doing these kind of local syntax previously: https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/provision/core/vvv/provision.sh#L62-L64

ah I think the problem is a mistake on my part, lsb_release vs lsb_release lsb_release

adjusted, and seems to be ran okay: https://github.com/Varying-Vagrant-Vagrants/VVV/actions/runs/11858839047/job/33050382482?pr=2739
let me know if it needs further adjustments

tomjn · 2024-10-20T15:18:55Z

provision/core/vvv/provision.sh

+    if dpkg --compare-versions "${OSVERSION_NUMBER[@]}" ge "24.04"
+    then
+      # to make it available globally this is the last workaround, hopefully it doesn't break the system
+      # TODO: try to find a better alternative way to install


is there somewhere I can read up on why this happens or where the fix came from? Would be good to have it in the comments, I've created a separate PR for shyaml fixes

https://peps.python.org/pep-0668/

https://pimylifeup.com/python-externally-managed-environment/

https://stackoverflow.com/questions/75608323/how-do-i-solve-error-externally-managed-environment-every-time-i-use-pip-3/75722775#75722775

provision/provision-helpers.sh

Co-authored-by: Tom J Nowell <[email protected]>

This reverts commit c705505.

This reverts commit 87ba465.

This reverts commit c798cef.

This reverts commit 30b8230.

This reverts commit bbcf60d.

This reverts commit 4c38733.

…beta # Conflicts: # provision/provision-helpers.sh

…r-provider # Conflicts: # provision/core/mariadb/provision.sh

…r-provider

This reverts commit 3e6aec5.

…r-provider

tomjn and others added 23 commits September 10, 2022 11:55

Merge branch 'develop' into stable

5b3aa20

Attempt to fix git safe dir issue

dd9691e

- wildcard

Fix git safe.directory script

312aed8

Merge pull request Varying-Vagrant-Vagrants#2652 from Varying-Vagrant…

d28080c

…-Vagrants/develop v3.11 PR

Merge pull request Varying-Vagrant-Vagrants#2669 from Varying-Vagrant…

3b367ce

…-Vagrants/develop 3.11.2 on stable

Merge pull request Varying-Vagrant-Vagrants#2684 from Varying-Vagrant…

aee9a69

…-Vagrants/develop 3.12 stable

Merge branch 'develop' into stable

f3ef893

Merge pull request Varying-Vagrant-Vagrants#2720 from Varying-Vagrant…

e0dad5d

…-Vagrants/develop v3.1.2 stable

Merge remote-tracking branch 'upstream/stable' into docker-provider-beta

12be863

# Conflicts: # provision/core/git/provision.sh

Merge remote-tracking branch 'upstream/develop' into docker-provider-…

cfd11ad

…beta

Update mariadb repo to OVH for ubuntu focal

3a9de05

- Add OVH url in hosts_to_test ( keep the mariadb.gb.ssimn.org )

Use mysql as service name in docker

4c38733

Use mysql as service name in docker -- vagrant_up

bbcf60d

Attempt to dynamically get mysql service name

30b8230

Fix inverted vvv_get_mysql_service_name

c798cef

Fix syntax issue

87ba465

- Better messages

More messages fix

fb41956

Attempt to add more Ubuntu noble repo list

80275ed

Dummy vvv sources list for noble

8d9dd89

Attempt to solve shyaml pip install

237b447

Fix dpkg version compare relation arg

3dc8769

Allow custom PHP CLI version

c705505

Use ubuntu 24.04 as default image for docker provider

e85f98a

Revert git safe dir setup

c72778f

pentatonicfunk requested a review from tomjn October 20, 2024 02:44

This was referenced Oct 20, 2024

Shyaml Ubuntu 24 fixes #2740

Open

MariaDB OVH Mirror #2741

Merged

tomjn reviewed Oct 20, 2024

View reviewed changes

config/default-config.yml Outdated Show resolved Hide resolved

tomjn reviewed Oct 20, 2024

View reviewed changes

config/homebin/vagrant_provision Outdated Show resolved Hide resolved

tomjn reviewed Oct 20, 2024

View reviewed changes

provision/core/mariadb/provision.sh Outdated Show resolved Hide resolved

tomjn reviewed Oct 20, 2024

View reviewed changes

provision/provision-helpers.sh Outdated Show resolved Hide resolved

pentatonicfunk and others added 15 commits October 21, 2024 12:43

Fix comments copy in provision/core/mariadb/provision.sh

33db168

Co-authored-by: Tom J Nowell <[email protected]>

Update Changelog

227a983

Revert "Allow custom PHP CLI version"

2367444

This reverts commit c705505.

Revert "Fix syntax issue"

6809d61

This reverts commit 87ba465.

Revert "Fix inverted vvv_get_mysql_service_name"

2d42d49

This reverts commit c798cef.

Revert "Attempt to dynamically get mysql service name"

754ac15

This reverts commit 30b8230.

Revert "Use mysql as service name in docker -- vagrant_up"

c544d5a

This reverts commit bbcf60d.

Revert "Use mysql as service name in docker"

196887e

This reverts commit 4c38733.

Merge remote-tracking branch 'upstream/develop' into docker-provider-…

d224835

…beta # Conflicts: # provision/provision-helpers.sh

Merge remote-tracking branch 'origin/docker-provider-beta' into docke…

060f8a0

…r-provider # Conflicts: # provision/core/mariadb/provision.sh

Minor script adjustment Varying-Vagrant-Vagrants#2739 (comment)

3e6aec5

Merge remote-tracking branch 'origin/docker-provider-beta' into docke…

ebf8675

…r-provider

Revert "Minor script adjustment Varying-Vagrant-Vagrants#2739 (comment)"

a6b4f7f

This reverts commit 3e6aec5.

Merge remote-tracking branch 'origin/docker-provider-beta' into docke…

0094cb0

…r-provider

Improve OS version number check on shyaml_setup

88418dd

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Docker Image to Ubuntu 24.04 ( Noble ) #2739

Update Docker Image to Ubuntu 24.04 ( Noble ) #2739

pentatonicfunk commented Oct 20, 2024

update-docs bot commented Oct 20, 2024 •

edited by unfurl-links bot

Loading

tomjn commented Oct 20, 2024

pentatonicfunk commented Oct 20, 2024

tomjn Oct 20, 2024

pentatonicfunk Oct 21, 2024

tomjn Oct 21, 2024

pentatonicfunk Nov 15, 2024

tomjn Oct 20, 2024

pentatonicfunk Oct 29, 2024

pentatonicfunk Oct 29, 2024

pentatonicfunk Oct 29, 2024

tomjn Oct 29, 2024

pentatonicfunk Nov 15, 2024

tomjn Oct 20, 2024

pentatonicfunk Oct 21, 2024

	local OSVERSION_NUMBER=$(lsb_release lsb_release -sr)
	local OSVERSION_NUMBER
	OSVERSION_NUMBER=$(lsb_release lsb_release -sr)

Update Docker Image to Ubuntu 24.04 ( Noble ) #2739

Are you sure you want to change the base?

Update Docker Image to Ubuntu 24.04 ( Noble ) #2739

Conversation

pentatonicfunk commented Oct 20, 2024

Checks

update-docs bot commented Oct 20, 2024 • edited by unfurl-links bot Loading

tomjn commented Oct 20, 2024

pentatonicfunk commented Oct 20, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

use upstream/develop branch

switch to origin/docker-provider

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

update-docs bot commented Oct 20, 2024 •

edited by unfurl-links bot

Loading

use `upstream/develop` branch

switch to `origin/docker-provider`