You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Networks and volumes for the project are always initialized when you do docker-compose run, even if they might not be required for that specific service.
Ho I see. So it's not a good practice to "mix" containers like this in a same docker-compose. I will create a docker-compose-build.yml to store all containers without network, thanks you.
When creating files in Go, the stdlib will create (and then rapidly
delete) files ending with `-go-tmp-umask` to determine the umask
to use for permission purposes.
This can cause trouble with Live Update because the files tend to
vanish underneath it, for example.
Fixesdocker#5117.
Given the following docker-compose:
Running
docker-compose -p toto run --rm maven ls
is creating a networkCreating network "toto_default" with the default driver
.Issue: docker-compose should not create a network when running a container that has no network!
Note: I can see a network is not created if all containers have
network_mode: "none"
The text was updated successfully, but these errors were encountered: