Missing image 29.0.7.1

[asm0dey]

My compose file:

services:
  redis:
    image: redis:alpine
  db:
    image: postgres
    restart: always
    volumes:
      - ./pg_data:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB_FILE=/run/secrets/postgres_db
      - POSTGRES_USER_FILE=/run/secrets/postgres_user
      - POSTGRES_PASSWORD_FILE=/run/secrets/postgres_password
    secrets:
      - postgres_db
      - postgres_password
      - postgres_user

  app:
    image: nextcloud:latest
    restart: always
    ports:
      - 8080:80
    volumes:
      - ./nextcloud:/var/www/html
    environment:
      - POSTGRES_HOST=db
      - POSTGRES_DB_FILE=/run/secrets/postgres_db
      - POSTGRES_USER_FILE=/run/secrets/postgres_user
      - POSTGRES_PASSWORD_FILE=/run/secrets/postgres_password
      - NEXTCLOUD_ADMIN_PASSWORD_FILE=/run/secrets/nextcloud_admin_password
      - NEXTCLOUD_ADMIN_USER_FILE=/run/secrets/nextcloud_admin_user

    depends_on:
      - db
    secrets:
      - nextcloud_admin_password
      - nextcloud_admin_user
      - postgres_db
      - postgres_password
      - postgres_user

secrets:
  nextcloud_admin_password:
    file: ./nextcloud_admin_password.txt # put admin password in this file
  nextcloud_admin_user:
    file: ./nextcloud_admin_user.txt # put admin username in this file
  postgres_db:
    file: ./postgres_db.txt # put postgresql db name in this file
  postgres_password:
    file: ./postgres_password.txt # put postgresql password in this file
  postgres_user:
    file: ./postgres_user.txt # put postgresql username in this file

I'm trying to migrate from my usual installation, but it's on the latest version as of now: 29.0.7, however after following the instructions on the migration, I get the error that it's impossible to downgrade data from 29.0.7.1 to 29.0.6.1.

[tzerber]

Looking at your nextcloud:latest your docker is downloading 29.0.6 ("NEXTCLOUD_VERSION=29.0.6" freshly pulled) .

Since I don't fully understand what's the problem here, by a wild guess I think you have a normal source / apt installation that you're trying to use inside docker OR you clicked the upgrade button inside the container, then deleted / recreated it without committing it . I suggest you wait a couple of days for the release of nextcloud:latest that is version 29.0.7. I would also suggest instead of latest to use specific version tags in order to avoid such issues, i.e. nextcloud:29.0.6-apache or nextcloud:29.0.6-fpm depending on your needs.

Edit: A reminder for everyone : Do backups before modifying any kind of software on your PC / server / production system. In the case of docker - commit the containers if you think things can go wrong and you want to "go back".

[asm0dey]

Yes, it was my intention to use a concrete tag, but the hope was that latest will be 29.0.7 :)
I will use my usual installation until then
Thank you

[tzerber]

Yes, it was my intention to use a concrete tag, but the hope was that latest will be 29.0.7 :) I will use my usual installation until then Thank you

Instead of "hoping" you can always check the https://hub.docker.com/_/nextcloud page and see the tags (scroll a bit down)

[asm0dey]

I see the tags indeed, but there are a lot of eventually consistent systems in the world. From my POV it's entirely possible that 29.0.7 is there, while the tag list is not updated yet :)

…

On Tue, 17 Sept 2024 at 00:44, Kaloyan Nikolov ***@***.***> wrote: Yes, it was my intention to use a concrete tag, but the hope was that latest will be 29.0.7 :) I will use my usual installation until then Thank you Instead of "hoping" you can always check the https://hub.docker.com/_/nextcloud page and see the tags (scroll a bit down) — Reply to this email directly, view it on GitHub <#2294 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ4XAQTDDVO6742UE2MMWLZW5NLRAVCNFSM6AAAAABOIXGYNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJUGE2TOMZUG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tzerber]

These tags on the page are generated automatically when new version is pushed, so if the hub page says 29.0.6-apache, 29.0-apache, 29-apache, apache, stable-apache, production-apache, 29.0.6, 29.0, 29, latest, stable, production⁠ then this is the image you're going to pull with "latest" . Most if not all docker images I've seen on the hub work that way. Also, it's a good practice to check the hub (or the docker repo holding the image, in case it's not the hub) to see if the version exists before you put it in the compose file.

[asm0dey]

No, you got me wrong :) Your assumption about mechanics of the tag list generation is correct, however there is no way to make sure that the tag list matches actual content of the repo. What happens if there was an error in API that generates the tag list and this error happened after the push was made?
Anyways, I'm sorry, I'm way out of the topics already. Thank you for the answer, please feel free to close the issue.

[stephanedupont]

I'm also stuck on a migration from non-docker instances of Nextcloud that I want to dockerize. I have updated to 29.0.7 before doing the migration, and as a result I can't finish it. Really hope that 29.0.7 image will be published imminently!

[Strit]

Any idea when dockerhub will get 29.0.7 or even 30?
As far as I can tell, there has been no PR submitted to them yet.

[isdnfan]

somehow it seems images for 29.0.7 and 30.0 build successfully https://github.com/nextcloud/docker/actions/runs/10913311149 but for some reason don't publish on hub.docker.com.. latest images there are 29.0.6 and 11d old :(

[joshtrichards]

somehow it seems images for 29.0.7 and 30.0 build successfully https://github.com/nextcloud/docker/actions/runs/10913311149 but for some reason don't publish on hub.docker.com

For the record, the reason for this is because it's a multi-step process since this image flows through the Docker Official Images program:

• one (or more) of us prepares things in this repo (version bumps, any necessary tag changes, any necessary base image bumps, any other PRs we want to get in for the next image release)
• one of us notifies the Docker Official Images team that we're ready to publish a new release and providing them with the appropriate commit hash/tag in our repo
• Docker Official Images team member reviews changes since the last release in collaboration with us and we address any issues/concerns together
• Docker Official Images team builds and publishes the real image

Disclaimer: I'm still learning the release process here, but that's the gist as I understand it.

P.S. Update was just approved on the Docker end as I wrote this: docker-library/official-images#17583 - once approved new images generally show up in < 24 hours

[isdnfan]

thank you for the explanation Josh. I was under impression Docker images process is fully automated.
new images are available already.