-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
running example job: failed to create container from image redis:latest: no such image #1080
Comments
Does this happen randomly or every time for you? |
everytime, and in all the nodes. |
Ah I didn't see that you are running it in a docker container. We don't really test for that use case currently so you are in a bit of uncharted territory. I would suggest that if you can, run Nomad outside of the container. Nomad client itself is acting as a supervisor and resource isolator. |
If nomad is connecting to the socket, should be no problem. Our policy enforce us to run any service under docker. We are testing Swarm and Kubernetes and all is running in docker containers. |
I've had similar problem. Sharing /tmp directory between host and a container fixed it. Docker service was exepcting to find the plugin file in host /tmp directory, but the file was created in the container filesystem:
|
The "no such image" error is a red herring, caused by a bug in go-dockerclient: fsouza/go-dockerclient#528 |
Adding a |
Hey @dadgar, I'm hitting this as well in the "happy path" to getting started with Nomad on Mac with the native docker client. First, I hit #1743, but that was an easy fix. Now, even though I am running Docker for mac and have the redis image downloaded, Nomad is still unable to find the image. I tried mounting the config {
image = "redis:latest"
port_map {
db = 6379
}
args = ["-v", "/tmp:/tmp"]
}
FWIW, I'm not running Nomad in a docker container; I'm running the native Docker client for mac. I think there's some missing communication though that's affecting both similarly. |
Another interesting observation point: Nomad actually instructs the Docker client to download the image (and it does), but then it can't find the image inside the local docker registry to boot. |
@sethvargo, the "no such image" error is misleading. See fsouza/go-dockerclient#528 |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
When trying to create a job example using the
nomad init
I get the following error:failed to create container from image redis:latest: no such image
The image was correctly pulled since making
docker images
,redis:latest
can be found.I am running 3 servers and 2 nodes inside of Docker in GCE, all setup using terraform
Nomad version
Nomad 0.3.1
Operating system and Environment details
CoreOS 983.0.0 (Coeur Rouge)
Running inside Docker 1.10.2
Nomad Client logs
Reproduction steps
client config:
server config:
Job file (if appropriate)
Default one, changing datacenter value
The text was updated successfully, but these errors were encountered: