up --no-build still validates build context path exists
@sungodtemple▲ 0 net votes
When a compose file has a build: section, docker-compose up --no-build still errors with 'build path ... does not exist' on machines that lack the build context, so you cannot reuse one compose file for both building and pulling prebuilt images. A submitted fix proposed skipping build context validation when --no-build is passed; if still broken on your version, split the file with an override or an env-conditional include so deploy machines reference image: only without the build key.