invalid service name

[japrescott]

I've updated docker to 1.3 and fig to 1.0 and suddently am getting strange "invalid service name" and "invalid repository name" errors and I am going apeshit finding a suitable approach. I like to camelCase things (e.g nodeWorker, or master_nodeWorker -> master is the folder name).
After getting the error that only [a-z0-9-_.] are supported, I changed to node.worker. Then it (I think its fig) says that it only accepts [a-zA-Z0-9]. After I changed that to node4worker, it complained about the _ in master_node4worker.
As these names were considered constants and are spread over many files, changing them is a real pain. Thus, I would be soooo greatful if you could please tell me HOW I should name my service/tag from 1.0< so that 1) fig doesnt blow 2) docker doesnt blow and 3) I can return to sanity
thanks for any tipps

[dnephin]

I think this might be a bug in docker 1.3, see discussion in #541

[japrescott]

good to know. thanks for your fast answer!

[magnars]

Any solution for using build in fig with docker 1.3?

[magnars]

I would also be really happy if I could use names with something other than [a-z0-9].

[dantoac]

as say in #541 (comment) changing the root folder name that contains the fig.yml to lowercase seem to solve the problem, at least for me.

[diasjorge]

I'm having the same problem. This makes creating a service with two_words or twoWords not working

[japrescott]

its a pain, I know, but until docker can set in stone how it is done (and fig can update accordingly), I just use lowcaps without underlines, dots or digits.

[nonsensery]

I think you can specify a project name on the command line:

cd My_Great_Project
fig --project-name mygreatproject up

or via an environment variable:

cd My_Great_Project
export FIG_PROJECT_NAME=mygreatproject
fig up

[raykrueger]

It seems we could solve this in fig.yml if we were allowed to set a tag in fig.yml or if fig allowed case insensitive regex matching on the tag name.

Building web...
docker build <- ('.', rm=True, tag=u'OHNOESUPPERCASE_web', nocache=False, stream=True)
docker build -> <generator object _stream_helper at 0x101881460>
Invalid repository name (OHNOESUPPERCASE_web), only [a-z0-9-_.] are allowed

If we could set a tag instead of auto-generating one...

web:
  tag: chive_on
  build: .

But, alas...
Unsupported config option for web service: 'tag'

[blop]

Hello,
Could someone still add support for dots in service name before the docker-compose stable release?
Or even more like [a-zA-Z0-9-_.]
Thanks.

[thaJeztah]

@oblop currently, compose needs to use a naming convention to be able to "find" the containers belonging to a project, so unfortunately that won't be possible until some features in docker are implemented. Also see #652 (comment) and #869 for more information on this.

[blop]

Make sense. Let's vote for a quick merge of moby/moby#9882 then ;)

[lox5773]

+1..
I also want service name to allow at least underscore and/or hyphen

[aanand]

@lox5773 it'll be allowed in Compose 1.4 - see #1181

[dnephin]

The service name now allows for _, -, and .

[okgemaltoprg]

Hey guys, it's related to this topic (and many similar). It looks like the container_name validity check is still too strict in comparison with what is allowed with docker client:
container_name: myapp-dev-cluster1-1519

Works with docker run but it's refused by docker-compose with error:
ERROR: for myapp Invalid container name ("myapp-dev-cluster1-1519"), only [a-zA-Z0-9][a-zA-Z0-9_.-] are allowed

docker-compose v.: 1.7.0-rc1

[dnephin]

That error is coming from the daemon. I just tried that name with docker 1.10.3 and it worked for me.

[okgemaltoprg]

I don't get it. If I do (with the same Docker daemon version) docker run --name=myapp-dev-cluster1-1519 ... it works. If it's in a compose file as mentioned in my comment #issuecomment-206406414 I get the error.

How can one docker daemon have two different responses on the same request? From my point of view: docker client = works, docker-compose = validation errror.

Docker version is 1.9.1 v1.10.3, this one is automatically installed by docker-machine on AWS Ubuntu AMI (default AMI).