Build failed: max depth exceeded

Docker Hub
1

Hi,

at the end of a “successfull build”, i.e. all lines in the Dockerfile executed successfully:

Removing intermediate container 7b69eb5166f8
max depth exceeded

If I remove the RUN commands in the Dockerfile there is no such message.

Any ideas what “max depth exceeded” means?

Regards

2

getting this too, did you ever resolve?

3

No, sorry. It was not so important for me. I’ve started from scratch again.

4

I get this too, and it’s while trying ot edit a file in place; here I’m trying to sed to the a destination file, whether I do it inline "sed -i" or redirect

COPY conf/jenkins.conf /tmp/jenkins.conf
RUN sed "s/JENKINS_FQDN/$JENKINS_FQDN/g" /tmp/jenkins.conf > /etc/nginx/conf.d/jenkins.conf
5

Did you guys ever get a resolution to this?

6

Has this problem been resolved?
I would like to know the solution.

I’m having trouble with it happening even after cleaning the environment as docker-compose down.

7

Oh. I’ve just solved that problem.

It seems that docker-compose down does not make it clean.

You need to use docker image prune -a to be precise.

Thanks to the author of the following article.