CODEWITHSUNDEEP
ddev
wizonesolutions
wizonesolutions

Reputation: 627

How do I debug a failing additional Dockerfile?

I have created .ddev/web-build/Dockerfile. It builds, but it doesn't do what I want. How do I figure out why? DRUD_DEBUG=1 ddev start doesn't show any additional output. I don't know the proper docker-compose command to try building it manually either. This does not work:

cd .ddev
docker-compose build web

because it needs specific environment variables that DDEV injects.

Upvotes: 0

Views: 332

Answers (1)

rfay
rfay

Reputation: 13045

The easiest way to see the build is ddev debug refresh, which will show you the whole build as it happens, with nothing cached.

You can also do the same thing manually:

cd .ddev
~/.ddev/bin/docker-compose -f .ddev-docker-compose-full.yaml build web --no-cache

and you'll see the full build go by. You can use additional build arguments as well to change the output format, etc. For example, ~/.ddev/bin/docker-compose -f .ddev-docker-compose-full.yaml build web --no-cache --progress=plain

You can review the entire Dockerfile that's being built at .ddev/.webimageBuild/Dockerfile.

See docs.

Upvotes: 3

Related Questions