Just to clarify: Your “old” .yml must be from like 2 years ago, because we did not changed the “names” of the container in the recent past, I looked it up (for reference)!
Thank you!!! I believe the --remove-orphans
was the fix, but I also changed the 127.0.0.1:9392:80 to 0.0.0.0:9392:80 as suggested in another post and we’re up and running with all of my data! I really appreciate your help and hopefully someone else can come out of the ‘darkages of .yml’ files with the suggestions on this thread. I certainly hadn’t updated mine in over 2 years.
Best Regards—
3 posts were split to a new topic: [Community Container] Only update specific images from Compose Files
Can you share what command you used to solve the problem
I believe this was the command that helped me, but it has been some time since I ran it:
It does take quite some time to resync the feeds after this update succeeds.
Issue resolved, in my case the solution was just ajust of the docker_composer.yml images:
Original:
mage: greenbone/XXX
New:
registry.community.greenbone.net/community/XXX
After that I runed the docker PULL and UP and after a bunch of time, the feeds are updated.
docker compose -f /docker-compose.yml -p greenbone-community-edition up -d notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects
docker compose -f /docker-compose_new.yml -p greenbone-community-edition up -d notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects
Please always take a look at the docs regularly if you have issues. The compose file might get important updates. For example the URL for the containers has already changed some month ago in the compose file.