error with autogenerated cluster name

[nikhilrayaprolu]

[surajnarwade]

@nikhilrayaprolu , can you paste your docker-compose file here ?

[surajssd]

@nikhilrayaprolu your env name is wrong, you cannot define env that has . dot in it. You can only have capital and small characters, dashes and underscores and numbers.

Also see the regex in the error:

a valid C identifier must start with alphabetic character or '_', followed by a string
of alphanumeric characters or '_' (e.g. 'my_name',  or 'MY_NAME',  or 'MyName',
regex used for validation is '[A-Za-z_][A-Za-z0-9_]*')

So change the name of env cluster.name to something else, similarly for all other envs.

I don't think kompose can do anything with this other than adding checks on our side. This comes from kubernetes.

[surajnarwade]

@nikhilrayaprolu , is your problem resolved, can we close this issue ?

[nikhilrayaprolu]

@surajnarwade @surajssd
here is my docker-compose.yml

version: '2'
services:
  yacy_mcp:
    build: .
    links:
      - elasticsearch
    ports:
      - 8100:8100

  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:5.5.0
    container_name: elasticsearch
    environment:
      - cluster.name=yacygrid
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
      - xpack.security.enabled=false
    ulimits:
      memlock:
        soft: -1
        hard: -1
    mem_limit: 1g
    volumes:
      - esdata1:/usr/share/elasticsearch/data
    ports:
      - 9200:9200
    expose:
      - "9300"
      - "9200"

    
volumes:
  esdata1:
    driver: local

[nikhilrayaprolu]

that is standard syntax by elastic regarding env variables
https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html

[surajssd]

@nikhilrayaprolu you can get some inspiration from elastic example in k8s repo or helm chart for elastic.

Also issue is filed with elastic upstream and PR to improve their docker-images to enable it to run on k8s.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[surajnarwade]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close