Docker Compose won't build image but tries to pull from Dockerhub - docker

Question

I have a docker-compose.yml file that defines multiple different services. Multiple of those services should be combined into the same image. They do refer to it in their definition. The first one has also the reference to the Dockerfile location, which should allow the build of this image. But since an update of Docker Desktop it seems to no longer be working.
The docker-compose.yml file looks something like this:
version: '3.9'
services:
frontend:
build: .
image: webapp
volumes:
- .:/app
working_dir: /app/src/frontend
command: yarn run serve
ports:
- 8080:8080
backend:
image: webapp
command: ./run_web.sh
env_file:
- .env
ports:
- 8081:80
depends_on:
- db
db:
image: postgres:13
volumes:
- db-data:/var/lib/postgresql/data
environment:
POSTGRES_USER: user
POSTGRES_DB: db
POSTGRES_PASSWORD: XXXXXXXXX
This worked perfectly fine until a few days ago, but now I get an error when trying to built the project.
WARNING: Some service image(s) must be built from source by running:
docker compose build frontend
Error response from daemon: pull access denied for webapp, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
What am I missing?
The Dockerfile is not very spectacular and it builds if I simply call it manually.
FROM python:3.7-stretch as base
RUN apt-get update && apt-get install -y \
curl \
unzip \
apt-transport-https \
&& rm -rf /var/lib/apt/lists/*
RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - \
&& echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list \
&& curl -sL https://deb.nodesource.com/setup_14.x | bash - \
&& apt-get update && apt-get install -y \
yarn \
&& rm -rf /var/lib/apt/lists/*
RUN pip install pip==21.1.1 poetry==1.1.6
WORKDIR /app/src/backend
FROM base as prod
COPY src/backend/poetry.lock src/backend/poetry.toml src/backend/pyproject.toml /app/src/backend/
RUN poetry install --no-dev
COPY src/frontend/package.json src/frontend/yarn.lock /app/src/frontend/
RUN cd /app/src/frontend && yarn install --prod
COPY src/ /app/src/

Answer 1

Ok, I've seen, that you're using the image name webapp in the frontend service and the backend service.
The frontend service has the build instruction included and will name the builded image webapp. The backend service does not have any build instruction and tries to pull the image webapp from the registry.