docker-elk: Cannot build docker images

I cloned the repo then when I tried to start it I face this issue.

$ docker-compose build
Building elasticsearch
Step 1/6 : ARG ELK_VERSION
ERROR: Service 'elasticsearch' failed to build: Please provide a source image with `from` prior to commit

Apparently it’s a known one ARG before FROM in docker. But this issue was closed and the problem solved in the docker project and am still facing it.

Here’s an overview of my environment:

$ docker version                                                                                                                        
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.8.3
 Git commit:   092cba3
 Built:        Thu Oct 12 22:34:44 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   092cba3
 Built:        Thu Oct 12 22:34:44 2017
 OS/Arch:      linux/amd64
 Experimental: false

Normally this version of docker handles ARG before FROM.

I tried to copy .env file into elasticsearch, logstash and kibana directories and I rebuild again with NO success.

Does anyone faced this issue before ?

Any help is appreciated. Thanks in advance

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 28

Most upvoted comments

It works smoothly now. Thanks 👍

@antoineco no, I don’t think so. It was may be due to another problem, because I couldn’t start any container with my docker service, even if it was running. So I finally remove it and re-install docker and docker compose. All is going fine now! Thanks !

@lakano the easiest thing you can do is checkout commit 1ac84fbe, or just revert commits up to this commit id.

Everything after that breaks compatibility with Docker < 17.05

Actually you’re right, just realized this landed in Docker 17.05, not 17.03. Apologies for that 🙏

Good point. That said 17.03 was validated against Kubernetes, but be careful if you use 18.xx.

Ah, good point, I was waiting for Searchguard 6.0 to update that branch, but I can push a fix independently.