You’d still need the docker mapping between the container and the host-computer, but now it would be 8080 → 8080. So, if you were using docker compose, it would be…
You probably can’t set that up in the Docker Desktop UI. It looks like the only options it offers for mapping ports would have to match an EXPOSE directive in the Dockerfile that made the original image.
Is there some reason you don’t want n8n to use port 5678 within docker?
FWIW, when you have a mapping in Docker from 8080 (“external” Docker-host-machine / workstation) to 5678 (for the n8n service on the “internal” Docker-container-network), the only port that would be visible to external firewall rules, etc. would be the “external” port (8080). It is unlikely that “enterprise security” rules / routing actually restrict or monitor ports, hostnames, or ip-addresses inside Docker.