Hello, I am currently trying to set up Discourse on a new machine. I checked out the discourse_docker repository and ran ./launcher rebuild app. (I skipped bootstrapping because I had configurations from before). Rebuilding resulted in the following output: WARNING: We are about to start download…

@Falco I have created a post on the Docker forums and got a reply. The problem is connected to DOCKER_CONTENT_TRUST=1. To reproduce this issue you can run the following commands: $ export DOCKER_CONTENT_TRUST=1 $ docker pull discourse/base:2.0.20191219-2109

Can you update docker to the latest version available for your OS and try again?

Thank you for your reply @Falco . I am running the latest version of Docker: Docker version 19.03.5, build 633a0ea838 See: Docker Engine version 29 release notes | Docker Docs Sorry, for not mentioning this before :roll_eyes:

So a simple docker pull discourse/base:2.0.20191219-2109 is failing?

[Bild] Falco: docker pull discourse/base:2.0.20191219-2109 Yes. This command fails the same way as described in my initial post: ERRO[0001] Metadata for targets expired ERRO[0002] Metadata for targets expired Error: remote repository docker.io/discourse/base out-of-date: targets expired at M…

That is very weird. Is your server clock right? Do you have any weird caching, firewall or something?

@Falco My clock seems to be synced: $ timedatectl status Local time: Fr 2019-12-27 19:57:48 CET Universal time: Fr 2019-12-27 18:57:48 UTC RTC time: Fr 2019-12-27 18:57:49 Time zone: Europe/Berlin (CET, +0100) …

I also want to mention that other containers run just fine. So it seems to be somehow related to the Discourse image.

Well, I can docker pull discourse/base:2.0.20191219-2109 just fine, across many OSs, in different cloud providers in different continents so I’d say it’s something particular to your local computer/docker install. As this comes from the docker service, try seeking help on https://forums.docker.com/ …

Will do @Falco . Thank you for your help so far :slight_smile:

Oh I see. Why did you set this flag on your local machine? It doesn’t come enabled by default in Ubuntu.

Discourse Docker-Images sind nicht signiert

Produktunterstützung Installation

Stephen (Stephen) 28. Dezember 2019 um 05:50 17

Da Sie derzeit von den Anweisungen für eine empfohlene Installation abweichen, wird dies als nicht unterstützt gekennzeichnet, damit andere denselben Fehler nicht machen.

Thema		Antworten	Aufrufe
500 Error trying to upgrade discourse Self-hosting	10	541	17. April 2024
Is Docker image discourse/discourse considered safe and production-ready? Self-hosting hosting	30	3561	26. Mai 2026
Community supported official docker image Development	35	9150	22. Juli 2022
Tag 1.3.10 not found on reload Product Support	6	1371	17. Januar 2017
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	111621	16. Januar 2025

Discourse Docker-Images sind nicht signiert

Verwandte Themen