Coffee not brewing ☕️ about coffee

[1um]

Nice, do you run Coffee docker from same folder as your FE code?

docker run --pull=always -it -e OPENAI_API_KEY=${OPENAI_API_KEY} -v $(pwd):/mount coframe/coffee:latest

In this command -v $(pwd):/mount is mirroring all files from current folder $(pwd) to /mount folder in docker.
I'll add check that /mount is not empty on startup.

[1um]

Scratch that, something else is an issue. What is filename of file you edit and OS you are using?

[petersolimine]

Yes, same directory. I'm on MacOS Monterey, M1 Chip. Filename is src/app/components/destinations.tsx

[saikrishnaklu1993]

Have same issue on windows - it doesn't recognize the coffee component.

on windows(inside the app dir):
docker run --pull=always -it -e OPENAI_API_KEY="xxxx" -v "${PWD}:/mount" coframe/coffee:latest

@petersolimine great thanks for opensourcing!!

[sam-shridhar1950f]

Same issue here on Windows. The coffee component isn't recognized despite running docker in the same directory.

[OmmAshutosh]

ssue could be related to permissions or the location of the Compose binary.Here are a few steps you can take to troubleshoot this issue:

1. which docker-compose; this should return the path to the Docker Compose binary. Make sure that this path is included in your system's PATH environment variable.
2. ls -l $(which docker-compose)
3. sudo chmod +x $(which docker-compose)
4. docker-compose --version
5. sudo chmod +x $(which docker-compose)
6. docker-compose --version
   Check for any conflicting Docker installations: Make sure that there are no other Docker installations on your system that could be conflicting with Docker Desktop. If there are, you may need to uninstall them before reinstalling Docker Desktop.

[mauricedb]

I am having the same issue using Windows. I have run into similar issues before with file watching inside a container and it seems that that is a known issue. See https://stackoverflow.com/a/70686685

I tried using docker-volume-watcher but didn't help as the bind was skipped since it has invalid source path.

I tried using the PollingObserver but that didn't work for me either, probably my lack of Python skills.
One thing I did notice, With the PollingObserver it would list the files/folders in the root of my Next.js target project

While with the Observer it didn't

When I run py .\main.py on my Windows machine it works just fine with a small issue of always duplicating the import Coffee from './components/Coffee'; line.