Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-compose up --no-build should not require the existence of the build context directories #7674

Closed
zeehio opened this issue Aug 17, 2020 · 5 comments

Comments

@zeehio
Copy link

zeehio commented Aug 17, 2020

Is your feature request related to a problem? Please describe.
In a production system, I would like to use docker-compose up --no-build but I can't when the build context directory does not exist, even though it is not used:

ERROR: build path my/build/context either does not exist, is not accessible, or is not a valid URL.

Describe the solution you'd like
docker-compose up --no-build should not require the existence of build context directories.

Describe alternatives you've considered
I can run mkdir -p my/build/context before docker-compose up --no-build, but it's kind of annoying to have to do that.

Additional context

Discussion at: https://stackoverflow.com/q/53389151/446149

@woo2
Copy link

woo2 commented Jan 22, 2021

Looks like this was fixed in 1.27.0!

@emranbm
Copy link

emranbm commented Apr 26, 2021

That's nice. Thanks.
But it still errors on docker-compose down:

ERROR: build path /some/where either does not exist, is not accessible, or is not a valid URL.

However, why does it need to have build context when downing at all?!

@emranbm
Copy link

emranbm commented Apr 26, 2021

This issue seems to be a subset of #4047.

@stale
Copy link

stale bot commented Oct 30, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 30, 2021
@stale
Copy link

stale bot commented Apr 17, 2022

This issue has been automatically closed because it had not recent activity during the stale period.

@stale stale bot closed this as completed Apr 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants