Pull access denied. Users are experiencing issues with Docker, specifically with the error message “pull access denied for local_discourse/app, repository does not exist or may require ‘docker login’”.
Justman10000 initially reported the issue and, after investigating the code, found that the launcher uses the image local_discourse/app if the variable $run_image is empty Justman10000. pfaffman suggested checking for firewalls and running docker run hello-world to test the installation, which Justman10000 reported was working correctly.
Justman10000 confirmed that they ran discourse-setup, but the issue persists. cbc404 reported the same issue on a fresh Debian 12 installation and shared their iptables configuration, but it did not seem to solve the problem cbc404. Justman10000 reiterates that the issue is likely due to the launcher trying to pull the non-existent image local_discourse/app:latest when $run_image is empty.
Hi, have this:
Unable to find image ‘local_discourse/app:latest’ locally
docker: Error response from daemon: pull access denied for local_discourse/app, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied.
See ‘docker run --help’.
I had a look at the code! Seems like the launcher uses local_discourse/app (wich not exists) as image if the variable $run_image is empty! This has the following code:
cat $config_file | $docker_path run $user_args --rm -i -a stdin -a stdout $image ruby -e \
"require 'yaml'; puts YAML.load(STDIN.readlines.join)['run_image']"
Do you have a idea?
Are you behind some kind of firewall?
Does
docker run hello-world
work?
Hello from Docker!
This message shows that your installation appears to be working correctly.
Did you run discourse-setup?
Yes, i did
I have the same exact problem, and have gone through the suggested steps. Debian 12 bookworm, docker installed from apt, 20.10.24+dfsg1, Bump.
iptables -S
-P INPUT ACCEPT
-P FORWARD DROP
-P OUTPUT ACCEPT
-N DOCKER
-N DOCKER-ISOLATION-STAGE-1
-N DOCKER-ISOLATION-STAGE-2
-N DOCKER-USER
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
So, this solved the problem?
The image also not exists?
Nah, that’s just my firewall’s configuration in case it’s relevant, I’m as clueless still as to what is causing this.. as my Debian is freshly installed.
Well, as I said, it tries to pull the image local_discourse/app:lates if the variable $run_image is empty!