docker-compose create should create network in default v2 setup

[clkao]

with v2 services are default to use project-scoped network, however the _default network isn't created during docker-compose create, at least for the first time the project is run with.

This simple docker-compose.yml fails with docker-compose create:

version: '2.0'
services:
  foo:
    image: nginx

[NeoMcFly]

+1

Was my blocking issue by doing create. With docker-compose up now it'is ok. Create should works as well.

[clkao]

I just noticed that down actually removes the network, so I can see that network creation being part of up is more symmetric.

If having the network creation in create is not desired default behaviour, perhaps we can add a additional option to create to do so?

[dnephin]

create is only for creating containers. The network is created by up, this is by design.

[NeoMcFly]

So create fails by design ?

[NeoMcFly]

I am fine with the idea that create doesnt create networks.

In the same time, create should not stop with error about missing ot the default network. The command docker-compose create need a fix. I see two ways :

1. create command create networks. (New design which is questionnable i guess)

2. or create doesnt matter about missing default network. It justs validate the whole networks consistency without creating it.

[dnephin]

Please include the output you get when running docker-compose create. It may be that we need to create the network first.

[clkao]

With the test yml file above as a.yml:

% docker-compose --version
docker-compose version 1.6.0, build d99cad6
% docker-compose -p foo -f a.yml create
Creating foo_foo_1
ERROR: network foo_default not found

[rpeleg1970]

+1
the workaround now is to create the default network upfront (using docker network create foo_default) but it feels awkward mixing docker and docker-compose calls, especially since you explicitly need to reference generated resource names.

[KalleDK]

I got the same problem - I'm guessing the same can be said about the volumes

[squeaky-pl]

This was also strange to me. Kind of against principle of least astonishment.

[aanand]

docker-compose create is supposed to be a close analogue to docker create, so that's an argument against overloading it with responsibilities.

However, given there's no way to create the networks/volumes beforehand, I'm not sure we can avoid doing that in create. (We use the same rationale with docker-compose run to pre-create networks, volumes and containers.)

[KalleDK]

I wouldn't mind if it was seperate from docker-compose create.. as in docker-compose volume create .. A command to create the volumes and/or the network used by a service.. So that I would be able to do

docker-compose ... volumene ..
docker-compose ... network ...
docker-compose create

And the reverse order for removal