Upgrading from version 13.5.4 -> latest

[verbeckii]

Hello

I am trying to update my Gitlab to the newest version due to a sudden miner inside GitLab docker (can find it with ClamAV ) Some related issues here: 2447 2488

So about my upgrading problem: I have Gitlab 13.5.4-ee And here my upgrading path 13.5.4->13.8.8->.13.12.15->14.0.11->latest(probaly it's ~14.4?) I'm stacked on 14.0.11->latest step Right now my Gitlab version is 14.0.11 and trying to pull the latest docker image docker pull gitlab/gitlab-ee:latest and start with docker-compose up -d won't finish upgrading...

So can you help me? what steps I should do to upgrade to the latest version? Also on 14.0.11 I'm waiting for background migration but seems it is a problem There are 6 failed tasks...

[kkimurak]

1. First of all, you are in the wrong place to ask a question. This is for sameersbn/gitlab, is community-driven unofficial and well-customized docker image, not official gitlab/gitlab-ee image. I think it is good idea to get enterprise support by official gitlab team.
2. Refer official documentation about upgrading https://docs.gitlab.com/ee/update/ , especially version-specific introduction.
3. There would be many reasons that "docker-compose up -d won't finish" you reported, so It is extremely hard for us (including gitlab team, of course) to estimate what is going wrong from your report. Please provide more detailed information for accurate support. One of the "information" is the logs on your gitlab container. If your container did not start up, check docker logs your-gitlab-container-name. If the container is up but you got 500, 502 or something, check log files in container.

Best,

[kamaldixitdevops]

@verbeckii Please check issue #2448 if that helps you. Mentioned some inside investigation of this issue.

[verbeckii]

1. First of all, you are in the wrong place to ask a question. This is for sameersbn/gitlab, is community-driven unofficial and well-customized docker image, not official gitlab/gitlab-ee image. I think it is good idea to get enterprise support by official gitlab team.
2. Refer official documentation about upgrading https://docs.gitlab.com/ee/update/ , especially version-specific introduction.
3. There would be many reasons that "docker-compose up -d won't finish" you reported, so It is extremely hard for us (including gitlab team, of course) to estimate what is going wrong from your report. Please provide more detailed information for accurate support. One of the "information" is the logs on your gitlab container. If your container did not start up, check docker logs your-gitlab-container-name. If the container is up but you got 500, 502 or something, check log files in container.

Best,

thanks for your answer

It though it is an official GitLab-docker repo So I should figure out how to upgrade to the latest version there BTW since my upgrade from 13.5.4 to 14.0.11 the last one works well

[verbeckii]

@verbeckii Please check issue #2448 if that helps you. Mentioned some inside investigation of this issue.

thanks for your answer

I can confirm that since my yesterday upgrade from 13.5.4 to 14.0.11 my miner issue was down I'm not sure if I need upgrdate to the latest but I think it will be good to prevent more potential security issue

[kkimurak]

@verbeckii I have to clarify - This is not a repository for official gitlab/gitlab-ee image. Here it is the repository for it. This repository, sameersbn/docker-gitlab, has been published as an unofficial image sameersbn/gitlab even before the official GitLab image gitlab/gitlab-ee was available.

That's why I told you are in wrong place. Your issue is out of scope. You can't expect to get a satisfying help. I just got sad to see you getting lost here.

Anyway, glad to hear your 14.0.11 works well. And I agree that using latest image is good choise for security reason.