You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use case
I am trying to debug via Cloud Code. My image is to be build like this docker build -t <target> -f <subdirectory_of_my_project>/Dockerfile. In <subdirectory_of_my_project> I have separate microservice that relies on code that is stored in "." of the project -- it is used in my many microservices. So I run docker build as shown above and have paths relative to "." in the microservice Dockerfile. However, when I try to debug via Cloud Code, the only option is to use context of directory where the Dockerfile is stored and where the argument "path" is pointing to. (This suggestion is because I looked into autogenerated scaffold file)
Feature
What if you added an ability to add "context" keyword, just like it exists in docker-compose files?
Something like
Use case
I am trying to debug via Cloud Code. My image is to be build like this
docker build -t <target> -f <subdirectory_of_my_project>/Dockerfile
. In <subdirectory_of_my_project> I have separate microservice that relies on code that is stored in "." of the project -- it is used in my many microservices. So I run docker build as shown above and have paths relative to "." in the microservice Dockerfile. However, when I try to debug via Cloud Code, the only option is to use context of directory where the Dockerfile is stored and where the argument "path" is pointing to. (This suggestion is because I looked into autogenerated scaffold file)Feature
What if you added an ability to add "context" keyword, just like it exists in docker-compose files?
Something like
The text was updated successfully, but these errors were encountered: