[BUG] docker-compose-plugin v2.17.2 error "name Does not match pattern '^[a-z0-9][a-z0-9_-]*$'"

[HenkAJV]

Description

I upgraded my Ubuntu Linux server from docker-compose-plugin v2.16.0 to 2.17.2.
The docker compose works without any issues on V2.16.

I now get the following error when I run docker compose -f ./application.yml up -d

name Does not match pattern '^[a-z0-9][a-z0-9_-]*$'
Should this not allow both upper and lower case characters?

Here is how my yml file looks like.
I think it's failing because I have Uppercase character (R and P) in the name string. I changed it to lowercase, and it works. Not sure if this is a correct or expected behaviour which is the reason, I am reporting it here.

version: '3.8'
name: main_fileservice_Redacted-Production
services:
  fileservice:
    image: Redacted.redacted.com:1400/fileservice:1.1.5
    container_name: File-Service-Redacted-Production-main
    volumes:
      - /opt/Redacted/File-Service-Redacted-Production/logs:/logs
      - /opt/Redacted/File-Service-Redacted-Production/encrypted.properties:/encrypted.properties:ro
      - /opt/Redacted/File-Service-Redacted-Production/encrypted.properties:/fileservice/encrypted.properties:ro
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    environment:
      - JDK_JAVA_OPTIONS=-Xms100m -Xmx1000m
    ports:
      - 8091:8091
    network_mode: bridge
    restart: unless-stopped

Steps To Reproduce

1. Latest Docker running (docker-compose-plugin v2.17.2) on Ubuntu V 20.0.4
2. Create YML file with name attribute using mixed characters (Uppercase, Lowercase, Underscore, dash)

• Example name: ThisIs_A_Test_name

3. run docker compose -f ./application.yml up -d

Compose Version

Docker Compose version v2.17.2

Docker Environment

No response

Anything else?

No response

[ndeloof]

application name indeed MUST be lowercase. Previous version did "normalize" the configured named, but this had this strange side effect for users to explicitly select and name but get resources to be created with a slightly distinct one. So 2.17 (actually, the underlying compose specification library) now validates configured name to match requirements.

[HenkAJV]

I saw the spec on the compose file and it all make sense.

Thank you. We can probably close this ticket.

[rzaccarias-ux]

has: n,
source: "/:username((?:@|%40)[%0-9a-zA-Z\(\).-]+)",
destination: "/at/:username"
}, {
has: n,
source: "/:username((?:@|%40)[%0-9a-zA-Z\(\).-]+)/subscribe",
destination: "/at/:username/subscribe"
}, {
has: n,
source: "/:username((?:@|%40)[%0-9a-zA-Z\(\).-]+)/:snapID",
destination: "/at/:username/:snapID"
}, {
has: n,
source: "/:username((?:@|%40)[%0-9a-zA-Z\(\).-]+)/highlight/:highlightID",
destination: "/at/:username/highlight/:highlightID"
}, {
has: n,
source: "/:username((?:@|%40)[%0-9a-zA-Z\(\).-]+)/highlight/:highlightID/:snapID",
destination: "/at/:username/highlight/:highlightID/:snapID"
}, {
has: n,
source: "/:username((?:@|%40)[%0-9a-zA-Z\(\).-]+)/preview",
destination: "/at/:username/preview"
}, {
has: n,
source: "/:username((?:@|%40)[%0-9a-zA-Z\(\)._-]+)/embed",
destination: "/at/:username/embed"
}],
beforeFiles: [],
fallback: []
},