Consul agent removed from nomad docker image

[Zortaniac]

Describe the bug
We noticed that consul was recently removed from the nomad docker image used for the nomad cluster nodes. This is now breaking our environment.
Since it is advised to have a dedicated consul agent for each node and the configuration is still containing the consul_config key.
We are wondering if it was intentional or a side-effect of migrating to a new repository for the image build?

To Reproduce
Run a nomad cluster with a consul configuration pointing to localhost.

Expected behavior
A consul agent should start as part of each nomad node.