Bobcares

Docker Max Depth Exceeded | How to Solve ?

by | Jun 13, 2022

Docker max depth exceeded error occurs when we use “build” and “image” at the same time and with the Dockerfile.

As part of our Docker hosting support service, Bobcares responds to all inquiries, big or small.

Let’s take a closer look at how our Support team handled the error: Service ‘api’ failed to build: max depth exceeded

Docker max depth exceeded: How to solve?

To resolve the error,we just need to execute docker system prune -a to remove any stopped container. This command deleted all the local docker images related to the dockerfile.

To fix the error, simply run docker system prune -a to remove any stopped containers. This command removed all local Docker images associated with the Dockerfile. The local storage has reached a limit after so many builds, and thus the error max depth has been exceeded.

As the number of images increases, so does the local storage, resulting in the error: max depth exceeded. The maximum depth does not indicate a storage-capacity error. Instead, it indicates that the api image we were creating had too many layers.

One plausible explanation is that we have a recursion as a result of having this in the compose file:


image: mhart/alpine-node:12
build: ./client

as well as this in a Dockerfile
FROM mhart/alpine-node:12

Every time we run our build, it adds a few layers to the local mhart/alpine-node:12 image. Running docker history mhart/alpine-node:12 confirms this. If this is the case, we should rename the image in the compose file.

Image parameter

In a docker-compose.yml definition, the image parameter for a service has two meanings, depending on whether or not a build parameter is present.

  • The image will be pulled and run if there is no build stanza.
  • If a build stanza is present, image will be the name of the built image that is tagged as, and run.

By naming the built image microsoft/mssql-server-linux, which corresponds to the FROM image microsoft/mssql-server-linux. Every time, Docker stacked the build on top of itself.

The initial build used the “official” microsoft/mssql-server-linux image, but subsequent builds used the local microsoft/mssql-server-linux image that had been appended to, until we reached the storage driver’s maximum number of layers.

For all images we create, use our own namespace:
version: "3"
services:
mssql:
build: .
image: 'user3437721/mssql-server-linux'

How to fix?

We’ll get the error “max depth exceeded” if we use “build” and “image” in the Dockerfile at the same time. Make sure we’re using a different image name than the one our Dockerfile starts with to solve this problem. Otherwise, each build will add layers to our “final image,” bringing us closer to the maximum depth.

Another consequence of this issue is that docker builds will always start from the beginning as if we had requested that the cache be disabled. This is because we’re updating the initial image with each build. Simply put, it does not update the image from which our build is based. The image builds will resume using the cache if we fix the docker-compose.yml file, which will be much faster.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, our Support team handled the error: Service ‘api’ failed to build: max depth exceeded

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

2 Comments

  1. clau

    You are de best !

    Reply
    • Krishna Priya

      Hello,
      Thank you for your feedback! We are delighted to hear that our article was helpful to you.

      Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF