unable to prepare context: path "../frontend" not found
larrryfisherthefisherman opened this issue · comments
This is what I get when I try and run: https://github.com/docker/awesome-compose/tree/master/react-rust-postgres
Preparing to clone inside a volume
Installing credential helpers...
done
Cloning into '/com.docker.devenvironments.code'...
Downloading tool to detect main repo language...
Done downloading.
Detecting main repo language...
Migration: no config.json detected
Migration: project is already configured for dev envs
2023/04/04 22:46:24 INFO: [core] [Channel #1] Channel created
2023/04/04 22:46:24 INFO: [core] [Channel #1] original dial target is: "npipe:////./pipe/buildkitd"
2023/04/04 22:46:24 INFO: [core] [Channel #1] parsed dial target is: {Scheme:npipe Authority: Endpoint:/./pipe/buildkitd URL:{Scheme:npipe Opaque: User: Host: Path://./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/04/04 22:46:24 INFO: [core] [Channel #1] fallback to scheme "passthrough"
2023/04/04 22:46:24 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: Endpoint:npipe:////./pipe/buildkitd URL:{Scheme:passthrough Opaque: User: Host: Path:/npipe:////./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/04/04 22:46:24 INFO: [core] [Channel #1] Channel authority set to "npipe:////./pipe/buildkitd"
2023/04/04 22:46:24 INFO: [core] [Channel #1] Resolver state updated: {
"Addresses": [
{
"Addr": "npipe:////./pipe/buildkitd",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2023/04/04 22:46:24 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first"
2023/04/04 22:46:24 INFO: [core] [Channel #1 SubChannel #2] Subchannel created
2023/04/04 22:46:24 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2023/04/04 22:46:24 INFO: [core] blockingPicker: the picked transport is not ready, loop back to repick
2023/04/04 22:46:24 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "npipe:////./pipe/buildkitd" to connect
2023/04/04 22:46:24 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0009026a0, {CONNECTING }
2023/04/04 22:46:24 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING
2023/04/04 22:46:24 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to READY
2023/04/04 22:46:24 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0009026a0, {READY }
2023/04/04 22:46:24 INFO: [core] [Channel #1] Channel Connectivity change to READY
2023/04/04 22:46:24 INFO: [core] [Server #4] Server created
2023/04/04 22:46:24 INFO: [core] [Channel #5] Channel created
2023/04/04 22:46:24 INFO: [core] [Channel #5] original dial target is: "npipe:////./pipe/buildkitd"
2023/04/04 22:46:24 INFO: [core] [Channel #5] parsed dial target is: {Scheme:npipe Authority: Endpoint:/./pipe/buildkitd URL:{Scheme:npipe Opaque: User: Host: Path://./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/04/04 22:46:24 INFO: [core] [Channel #5] fallback to scheme "passthrough"
2023/04/04 22:46:24 INFO: [core] [Channel #5] parsed dial target is: {Scheme:passthrough Authority: Endpoint:npipe:////./pipe/buildkitd URL:{Scheme:passthrough Opaque: User: Host: Path:/npipe:////./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/04/04 22:46:24 INFO: [core] [Channel #5] Channel authority set to "npipe:////./pipe/buildkitd"
2023/04/04 22:46:24 INFO: [core] [Channel #5] Resolver state updated: {
"Addresses": [
{
"Addr": "npipe:////./pipe/buildkitd",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2023/04/04 22:46:24 INFO: [core] [Channel #5] Channel switches to new LB policy "pick_first"
2023/04/04 22:46:24 INFO: [core] [Channel #5 SubChannel #6] Subchannel created
2023/04/04 22:46:24 INFO: [core] [Channel #5 SubChannel #6] Subchannel Connectivity change to CONNECTING
2023/04/04 22:46:24 INFO: [core] [Channel #5 SubChannel #6] Subchannel picks a new address "npipe:////./pipe/buildkitd" to connect
2023/04/04 22:46:24 INFO: [core] blockingPicker: the picked transport is not ready, loop back to repick
2023/04/04 22:46:24 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000902bf0, {CONNECTING }
2023/04/04 22:46:24 INFO: [core] [Channel #5] Channel Connectivity change to CONNECTING
2023/04/04 22:46:24 INFO: [core] [Channel #5 SubChannel #6] Subchannel Connectivity change to READY
2023/04/04 22:46:24 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000902bf0, {READY }
2023/04/04 22:46:24 INFO: [core] [Channel #5] Channel Connectivity change to READY
unable to prepare context: path "../frontend" not found
exit status 17
@larrryfisherthefisherman you say:
This is what I get when I try and run: https://github.com/docker/awesome-compose/tree/master/react-rust-postgres
What command are you running?
When I run:
docker dev create https://github.com/docker/awesome-compose/tree/master/react-rust-postgres --name rrp
I get a similar error, only in my case the end result is
unable to prepare context: path "../backend" not found
error: exit status 17
After cloning the react-rust-postgres
project with the above docker dev create ...
command, which failed as described, I am able to successfully run the app with docker compose up -d
.
There must be something special about the docker dev environment that we're both missing, but I have been researching this issue (with the help of phind.com) all day without success.