Alin Voinea
Alin Voinea
@pnicolli Nope, they are not. See https://github.com/docker-library/official-images/blob/master/library/plone And an update PR https://github.com/docker-library/official-images/pull/11795/files And the ARM architectures where remove by: - https://github.com/docker-library/official-images/pull/11303/files - https://github.com/docker-library/official-images/pull/11291/files
@pnicolli If you have the possibility to build and test the images on ARM architectures we can re-include them when we do the PR to official-images for #168 and #169
@pnicolli Would be nice if we would be able to test on ARM via github actions :exploding_head:
@iham As I have almost no experience with multi staging builds, don't fully rely on my opinion, but I tend to like your proposal. I also think that this will...
@pnicolli All versions should be pinned to versions.cfg, but yes the `-N` option would be more secure. > and just run the collective.recipe.plonesite specific part of the buildout? Can we...
@nutjob4life Indeed: We have: https://github.com/plone/plone.docker/blob/a516871e08532c8a343f9e9e713c8abc8d80aae6/5.2/5.2.4/debian/docker-initialize.py#L83 while: https://github.com/plone/plone.docker/blob/a516871e08532c8a343f9e9e713c8abc8d80aae6/5.2/5.2.4/debian/docker-initialize.py#L40 A PR would be appreciated :wink:
@jenkins-plone-org please run jobs
As with this we're moving away from Basic-Auth at the Zope root level, @plone/framework-team should also have a look into it.
@jenkins-plone-org please run jobs
Looks like the Jenkins test are failing again, unrelated to this PR.