"typo3/core-testing-docker" is not usable after rebuild for core ci
The typo3/core-testing-docker
Dockerfile has been changed to use
newer version of the docker image and to match the version for the
typo3/core-testing-docker-dind
image.
This generally builds and is already released to docker hub with versions >1.2.0. However, these versions cannot be used in TYPO3 core ci as it leads to some weired behaviour and issues:
- error message for the dind image stating that the ssl certificate folder cannot be mounted / are your root ? question
- all acceptance install tests and 2 acceptance fails badly, only because of this new image
- it looks like images used by
Build/Scripts/runTests.sh
are always pulled not using the proxy registry. Eventually this is a wrong assumption due the fact the "pull" progress lines are now displayed in the output.
Therefore, for TYPO3 branches 10.4, 11.5, 12.1 and main the docker
image typo3/core-testing-docker
is pinned to 1.1.0, which is the
latest working version. For the typo3/core-testing-docker-dind
image the latest tag is used, as this workes.
During two weekens I could not find a working build, therefore left the state as described for now.
We need to investigate this further to avoid a to big split between the docker and the docker-dind version.
Note: The custom docker-dind image build is needed as a workaround for the GitLab Runner HealthCheck issue regression introduced with GitLab Runner v15.1 until now (15.9). Due other issues (pending jobs) the decision was made to use the workaround in the hope to mitigate the pending jobs issue.
See pipeline: https://git.typo3.org/typo3/CI/cms/-/pipelines/38794