open-nomad/drivers
Mahmood Ali 844fd47acc Use user provided image name to launch container
This allows the container to be tagged with a user friendly image name
(e.g. `redis:3.2`) rather than the image ID (e.g.
`sha256:87856cc39862cec77541d68382e4867d7ccb29a85a17221446c857ddaebca916`).

Useful for human debugging, as well as some debugging and image scanning
tools.

This risks two bad changes:
1. Discrepancy in image resolution between docker and Nomad's image
loader.
  * I checked the image creation paths in Nomad, and noticed that we
either pulled the image or inspect the image with the user provided
name.

2. A race in image tagging where the tag is modified between image
loading and container creation.
  * I, personally, don't think this case is cause for concern, as it is
analogous to the task running a bit later.  As long as the image is
still present, creating the container should be good.
2018-11-27 16:12:15 -05:00
..
docker Use user provided image name to launch container 2018-11-27 16:12:15 -05:00
exec Merge pull request #4868 from hashicorp/b-plugin-ctx 2018-11-13 10:26:53 -08:00
java Merge pull request #4858 from hashicorp/b-fix-master-20181109 2018-11-13 16:08:26 -05:00
mock client: interpolate driver configurations 2018-11-15 16:25:57 -08:00
qemu Plugin client's handle plugin dying 2018-11-12 17:09:27 -08:00
rawexec Merge pull request #4868 from hashicorp/b-plugin-ctx 2018-11-13 10:26:53 -08:00
rkt Plugin client's handle plugin dying 2018-11-12 17:09:27 -08:00
shared/eventer docker: add default blocks for driver plugin config schema 2018-11-19 22:59:18 -05:00