MAybe there is nothing to build. Are you sure you want to build an image and not run containers? That would be a different command. And if you have nothing to build, compose will not do anything, therefore it will not show anything in the output (maybe it should). If you want to run containers, this is the command you need
docker compose --env-file .env.file up -d
If this is not what you need, share your compose file.
Hey, I had the same issue. Make sure that a Dockerfile exists in the directory where you run this. Or better yet make sure you have a “build:” section in your docker-compose file. This should specify the location of the dockerfile, like so:
I have the same problem, the build does not launch without response, no log nothing. I’m using wsl docker dekstop and nothing’s happening. I’m using the latest version v4.33.1, a tool that provides no log, Where should you look? The DockerFile, the docker-compose, the docker Desktop, I’ve deleted reinstall, up down, build specif build, no-cache, etc., etc., etc… I’ve got zero information, I’ve never seen such crap!
Please, share the commands and a Dockerfile and compose file that can reproduce the issue. As you can see in the previous post, we only experience this when there is nothing to build.
When you share these files and commands, format your post using code blocks as described hre
I’ve been using docker on Linux with the same project for several months and have never noticed any problems. But this week I wanted to test the same project on Windows with docker dekstop and wsl2, I mounted a symbolic link of my project, and I also have directories that I mount. My dockerfile and docker.compose are relatively complex. I think docker can’t detect the changes because it doesn’t understand the difference between the symbolic link c/mnt/project, c:/project, and /project…in short, it doesn’t work and it doesn’t say anything.It’s crazy that we don’t have a log somewhere that tells us, this directory doesn’t have any changes…
Again, you can tell us how bad Docker Desktop is, but we can only help if you help us with a file you tested and know it didn’t work. If I see the same issue, I know what I have to solve or report, but even if you say you exprience the issue with all your projects, it doesn’t mean I will be able to reproduce it. If your project is complex, you can make a smaller one that has the same or similar result. That we can try quickly without spending hours on discussions to understand what and how you did.
I can imagine problems with symlinks but based on your description I could not make an example project myself. A symlink is a pointer on Linux to another file, but but I don’t remember how it is stored on Windows so you could mount it. In any case, you should have some output somewhere and maybe you have just couldn’t find. It is entierely possible that we completely misunderstand your issue and it is different from the other problems discussed in this topic.
You could also enable WSL integration and work from the WSL distribution on Linux. That would mean your files would be on Linux and symlinks would be compatible with the client side and the container.
So in short, if you can provide some code we can try, we can help.
Thanks rimekek, you Can reproduce the problem with this steps : Docker Desktop, go to Settings >> Resources >> WSL Integration Ubuntu C:/project
Go terminal WSL
And what do you expect to build and why? Please, quote the part from the compose file or anywhere that indicates it should build docker images. As I see, there is no build definition in the compose file at all. So as I wrote
Did you see a tutorial somewhere that asked you to run the build command? If you did, are you sure that it referred to the same compose file you tried?
