Compose: Relax restrictions on service names

[aanand]

Now that we're not relying on a strict container name format, we should be able to allow more characters in service names, as has often been requested (see #799, #869, #941, #1300, #1384).

• Docker allows [a-zA-Z0-9_.-] (daemon.go)
• Compose allows just [a-zA-Z0-9] (service.py)

Any good reason we can't allow _.- now?

[thaJeztah]

:+1: I'll finally be able to build my

a_.--.__.--.__.--.__.--.__.--.__.--.__.--.__.--._ and 127.0.0.1:443 containers :D

[aanand]

Also relevant: allowed characters in image tags, since those are also based on service name. Seems to be the same chars though (tags.go).

[burritoIand]

+1

[ghost]

Is there anything new here? Will this change be part of the next RC or is it already baken into the current one?

[aanand]

1.3 is in code freeze, so this will not be in the next release.

[phazei]

Is there anything happening with support on this?
In this comment https://github.com/docker/compose/issues/472#issuecomment-91252147 it's mentioned that there should be some support for this in 1.3.

I'm using 1.3 and it doesn't seem to be any different. Will there be a 1.3.1 or will we need to wait till 1.4 till anything other than [a-z0-9] is allowed for reasons of service/container/host compatibility/bug?

[aanand]

This won't be in 1.3, or any 1.3.x release. 1.4 is the likely target.

[aanand]

Closed by #1624.