2318 commits behind...

dazza120

@savona rename those folders then got pull, then you can delete once MM is working on the new version

savona

@dazza120 But then if I rebuild the docker container wouldn’t it just put me back 2318 commits?

UPDATE: Yes, I rebuilt the docker container and it reverted right back.

savona

bhepler

@savona - Would it make sense to build from image, rename the git files, pull, update and then upload the fixed image as a PR?

savona

but I saw that the originator of the docker image said it was updated daily with a cronjob on this post:

idoodler

@savona Both package-lock.json can just be deleted. Did you intentionally change the files in the default directory?

savona

@idoodler No I did not change the default directory at all. That is why this is so odd to me.

rummyr

I got a message saying my MM was out of date, so I pulled the new docker image and now have the 2318 message also.

The top of my CHANGELOG.md reads “## [2.5.0] - 2018-10-01”
Though the “image date” as reported by Portainer is “Created 2019-01-01 15:08:22”

Do we need to wait for bastilimbach?

idoodler

@savona OK, you may have a corrupt git directory then. You may try to clone it again.

savona

I just blew away the docker image and did a new pull and it is fixed and on 2.6.0.

grep version package.json

“version”: “2.6.0”,