Page MenuHomePhabricator

Determine the steps for upgrading from the old Docker images to the new Docker images
Closed, ResolvedPublic

Description

We are in the process of sunsetting the "old" Wikibase Docker images and publishing our new Docker images (referred to hereafter as V1). Therefore, users will need instructions for how to transition to using V1.

As a Wikibase Operator, I want instructions for how to move from the "old" Wikibase 1.34 or 1.35 Docker images to the new V1 Docker images so that I can more confidently transition to using the newest version of Wikibase software.

For engineers, this could entail:

    • Minimally: instructions for how to backup/restore into the new V1 images (after testing to ensure it works)
  • Ideally: determining and documenting the steps necessary to upgrade from the most commonly used version of the old images to the V1 images

Please note that the upgrade instructions for V1 to V2 of the new images are not within the scope of this ticket. That need is captured elsewhere.

Event Timeline

That's cool!
The tasks talks about updating from any V0/V1 docker images versions 1.34 or 1.35.
Upgrade tests seem to cover 1.35, lts (i.e. 1.35), 1.33, and 1.32. Mind explaining the discrepancy to an ignorant manager?

That's cool!
The tasks talks about updating from any V0/V1 docker images versions 1.34 or 1.35.
Upgrade tests seem to cover 1.35, lts (i.e. 1.35), 1.33, and 1.32. Mind explaining the discrepancy to an ignorant manager?

I seem to have forgot about 1.34, this should add it https://github.com/wmde/wikibase-release-pipeline/pull/158

'1.32-base', v0
'1.33-base', v0
'1.34-base', v0
'1.35-base', v0
'latest-base', v0
'lts-base', v0
'wmde.0' <------ v1

Brilliant, thanks. I take migrating from 1.32 and 1.33 is not really essential, but was added as it is kind of working the same way?

Brilliant, thanks. I take migrating from 1.32 and 1.33 is not really essential, but was added as it is kind of working the same way?

yes I think that was oldest version I got working in the same way.

I lightly edited Tobias' doc, which has been merged and I think satisfies this ticket's requirements:

https://github.com/wmde/wikibase-release-pipeline/blob/main/docs/topics/upgrading.md

If the group agrees this is sufficient I will link to this doc from the MediaWiki pages.

Hi,

I was previously using the "bundle image" (wikibase/wikibase:1.35-bundle) as documented here: https://github.com/wmde/wikibase-docker/tree/master/wikibase but this github repo has not been updated (yet?).
I see that the new 1.35-2 image has also been published on docker hub in a different repo (wikibase/wikibase-bundle instead of wikibase/wikibase).

I've read the new upgrade guide but it's not clear if the upgrade path will work from 1.35-bundle to 1.35.2-wmde.1.
It would be useful I think to document this new image here https://github.com/wmde/wikibase-docker/ (is it also a "bundle image"? what are the included extensions?)

Thanks!

The docker pipeline has some environment settings; the bundle lists all extensions included in the new 'v1' images.

Not sure if it's documented elsewhere. Probably should be; people will end up at repos - past and present, thanks to existing links - and anywhere images are distributed.

As I understand it, the wikibase-docker repository is deprecated - if so, this should be noted clearly in the readme there, with links to the new location.

Thank you (again!) GreenReaper. Indeed, the wikibase-docker repo should be archived, with a clear link to wikibase-release-pipeline if the former is meant to be replaced by the latter.

However, I think updating the repo, instead of starting another and creating some confusion, may have its own advantages. Is there some project management or governance issues I'm not aware of?