Invalid repository name (Docker_app), only [a-z0-9-_.] are allowed

[EwanValentine]

I keep getting errors such as Invalid repository name (Docker_app), only [a-z0-9-_.] are allowed

Here's my fig.yml:

app:
  build: app/
  links:
    - redis
    - mysql
  volumes:
    - ./app/project:/var/www

nginx:
  build: nginx/
  ports:
    - 8080:80
  links:
    - fpm
  volumes_from:
    - app
  environment:
    <APP_SERVER_NAME>: dev-machine

fpm:
  build: fpm/
  links:
    - redis
  volumes_from:
    - app
  environment:
    APP_SERVER_NAME: dev-machine

mysql:
  image: mysql:latest
  ports:
    - 3363

redis:
  image: redis:latest
  ports:
    - "6379:6379"

Cheers!

[thaJeztah]

I think this issue is fixed in the latest builds, but as a workaround, rename your project directory from Docker to docker (lowercase).

[kojiromike]

…Or just set the environment variable FIG_PROJECT_NAME

[thaJeztah]

Both options should work as a workaround.

I checked, and it seems this is not yet fixed, but this issue is a duplicate of #655, @EwanValentine if you agree, could you close this issue so that the discussion can take place on a single location and keep the issue tracker "clean"? Thanks!

[aanand]

Also, this was fixed in #568

[aanand]

@EwanValentine Give Compose 1.1.0 RC2 a try, it contains the fix: https://github.com/docker/fig/releases/tag/1.1.0-rc2

[thaJeztah]

Ah, thanks @aanand I seemed to remember it was, but couldn't find the PR.

[EwanValentine]

Ohhhhh yeah! Perfect, thanks folks! :)

[cddr]

This seems broken again on 1.2.0

Whats more there appears to be an inconsistency in the format of names that accepted. For example first, using "foo_bar", I get...

vagrant@vagrant:~$ docker-compose up
Invalid service name "foo-bar" - only [a-zA-Z0-9] are allowed

...so I can go with FooBar then right? Nope.

vagrant@vagrant:~$ docker-compose up
Recreating vagrant_db_1...
Creating vagrant_FooBar_1...
Building FooBar...
Invalid repository name (vagrant_FooBar), only [a-z0-9-_.] are allowed

[aanand]

@cddr You're describing a different problem (uppercase characters in service names, not project names). See #1416.