Nomad should choose the default pause container based on system architecture #8926
Labels
stage/accepted
Confirmed, and intend to work on. No timeline committment though.
theme/consul/connect
Consul Connect integration
type/enhancement
Milestone
Nomad version
Nomad v0.12.4 (8efaee4)
Operating system and Environment details
Ubuntu 20.04 on ARM64
Consul v1.8.4
Issue
Nomad should choose the default "pause" container based on system architecture, instead of always defaulting to the AMD64 image.
When deploying a job with a Consul Connect-enabled service on Nomad on an ARM64 system without specifying the
infra_image
, Nomad pulls the AMD64 pause container. This causes the pause container to exit with the errorexec user process caused "exec format error"
, which causes the envoy container to exit with the errorFailed to start container ***(envoy container id)***: API error (409): cannot join network of a non running container: ***(pause container id)***
, which prevents Consul Connect from working (and any sibling tasks from running).Reproduction steps
Run any job with a Consul-Connect enabled service on Nomad installed on an ARM64 machine, with the
infra_image
not specified in the Nomad agent config. For example, the example countdash job.The text was updated successfully, but these errors were encountered: