HDM container fails to start "unable to start container process: error during container init: sethostname: invalid argument: unknown"

[davidsandilands]

Following the default and taking the latest HDM module and latest Docker module and including HDM on primary. When it tries to start the container it gets

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: sethostname: invalid argument: unknown
Error: failed to start containers: hdm

[tuxmea]

@davidsandilands can you please check if the error occurs when using hdm::version: '0.0.4'?

The puppet code still refers to 'main' as default version.

[davidsandilands]

I tried 0.0.4 and get the same message.

[davidsandilands]

I'm using PE 2021.7 on alma 8 and just a node group doing an include of HDM to the primary

[tuxmea]

@davidsandilands I can not reproduce this issue. Using vagrant and almalinux/8 image:

    1  curl -JLO 'https://pm.puppet.com/cgi-bin/download.cgi?dist=el&rel=8&arch=x86_64&ver=latest'
    2  tar zxf puppet-enterprise-2021.7.1-el-8-x86_64.tar.gz
    3  hostname
    4  cd puppet-enterprise-2021.7.1-el-8-x86_64
    5  ./puppet-enterprise-installer
    6  puppet agent -t
    7  puppet infrastructure console_password --password=xxxxxxxx
    8  puppet module install puppetlabs-docker
    9  puppet module install betadots-hdm
   10  puppet module install betadots-hdm --ignore-dependencies
   11  vi /etc/puppetlabs/code/environments/production/manifests/site.pp
   12  puppet agent -t
   13  history

HDM comes up and runs on port 3000.

This is my puppet module list:

/etc/puppetlabs/code/environments/production/modules
├── betadots-hdm (v1.2.3)
├── puppetlabs-apt (v9.0.1)  invalid
├── puppetlabs-docker (v6.0.2)  invalid
├── puppetlabs-powershell (v5.2.0)
├── puppetlabs-pwshlib (v0.10.3)
└── puppetlabs-stdlib (v8.5.0)
/etc/puppetlabs/code/modules (no modules installed)
/opt/puppetlabs/puppet/modules
├── puppetlabs-bash_task_helper (v2.0.0)
├── puppetlabs-cd4pe_jobs (v1.5.0)
├── puppetlabs-enterprise_tasks (v0.1.0)
├── puppetlabs-facter_task (v1.1.0)
├── puppetlabs-facts (v1.4.0)
├── puppetlabs-orchestrator_internal (v1.0.1)
├── puppetlabs-package (v2.2.0)
├── puppetlabs-pe_bootstrap (v0.3.0)
├── puppetlabs-pe_concat (v1.1.1)
├── puppetlabs-pe_databases (v2.2.0)
├── puppetlabs-pe_hocon (v2019.0.0)
├── puppetlabs-pe_infrastructure (v2018.1.0)
├── puppetlabs-pe_inifile (v1.1.3)
├── puppetlabs-pe_install (v2019.8.10)
├── puppetlabs-pe_nginx (v2017.1.0)
├── puppetlabs-pe_patch (v0.13.0)
├── puppetlabs-pe_postgresql (v2016.5.0)
├── puppetlabs-pe_puppet_authorization (v2016.2.0)
├── puppetlabs-pe_r10k (v2016.2.0)
├── puppetlabs-pe_repo (v2018.1.0)
├── puppetlabs-pe_staging (v0.3.3)
├── puppetlabs-pe_status_check (v2.4.0)
├── puppetlabs-pe_support_script (v3.3.0)
├── puppetlabs-powershell_task_helper (v0.1.0)
├── puppetlabs-puppet_conf (v1.3.0)
├── puppetlabs-puppet_enterprise (v2018.1.0)
├── puppetlabs-puppet_metrics_collector (v7.1.1)
├── puppetlabs-python_task_helper (v0.5.0)
├── puppetlabs-reboot (v4.2.0)
├── puppetlabs-ruby_task_helper (v0.6.1)
└── puppetlabs-service (v2.2.0)

[davidsandilands]

@tuxmea I have found the issue I believe this is due to docker limits on hostname length which I think shouldn't be greater than 63 characters. Due to azures default domain names being long (.msicadrzxlxerlviydrr0jdv2f.zx.internal.cloudapp.net) this pushed it over the edge. Providing just host name to the hostname parameter without domain resolved issue for me,