Open ChristianKniep opened 5 years ago
I found this also and was able to work around it by specifying the name field. Using your example yml:
version: "3.7"
services:
boedde:
image: boeddenstedt/audio-tour:2019-06-06.1
networks:
-boedde_proxy
deploy:
labels:
traefik.port: "80"
traefik.backend: "boedde"
traefik.frontend.rule: "Host:boedde.qnib.org"
networks:
boedde_proxy:
external: true
name: ingress_www
Description
I use traefik as a proxy to allow multiple subdomains to be served under the same HTTP/HTTPS ports.
The traefik service uses the network
ingress_www
.To decouple the proxy service from the other service artifacts I created an additional dockerapp to hook into the traefik infrastructure. But when I fire this up:
Describe the results you received:
The
docker-app
commands seems to encapsulate the networks for the installation, ignoring theexternal: true
statement. I derive that from theCreate network
statement.Describe the results you expected:
I would have expected, that external networks are still possible. When I carve out the docker-compose.yml part and deploy it as a stack, it just updates the service.
Output of
docker version
:Output of
docker-app version
:Additional environment details (AWS, VirtualBox, physical, etc.): Running ubuntu 18.04 on a VMware node.