I’m running, successfully, nc on a omv docker installation. When I did the security scan I result was an A but with Running Nextcloud 31.0.0.18 it is NOT on latest patch level
I just did a pull of the latest docker versions.
Could it be that the docker images lag behind? the nextcloud compose part is
nextcloud:
image: nextcloud
container_name: nextcloud
restart: unless-stopped
I guess you are on 30.0.8. that’s the latest stable. 31.0.2 is maybe not regarded as stable enough. Nextcloud AIO dies also only update after a few minor releases.
No, they do not lag behind (well sometimes a few days at most). v31.0.2 of the image is definitely published.
When I did the security scan I result was an A but with Running Nextcloud 31.0.0.18 it is NOT on latest patch level
What’s the date listed on the scan output? Sure it doesn’t need a refresh?
You can see release announcements here for the image:
Nextcloud Docker Release announcements
Also, are you sure you’re pulling from Docker Hub?
The non-AIO image set (which this appears to be) has the stable tag pointed at 30.0.8 currently, but the Compose posted by OP doesn’t have a tag on it so it just pulls the default (which is always the latest in Docker land).
Thanks!
In omv I did a download
export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; docker compose --file ‘/pool0/compose/Next Cloud/Next Cloud.yml’ --file “/pool0/compose/Next Cloud/compose.override.yml” --env-file ‘/pool0/compose/global.env’ --env-file ‘/pool0/compose/Next Cloud/Next Cloud.env’ pull 2>&1
nextcloud Pulling
collabora Pulling
redis Pulling
nginx-proxy Pulling
nextclouddb Pulling
nextcloud Pulled
collabora Pulled
nextclouddb Pulled
redis Pulled
nginx-proxy Pulled
END OF LINE
but it did not get the current version
What did you do after the pull?