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 command show error on running #933

Open
cor277 opened this issue Dec 24, 2023 · 10 comments
Open

Docker command show error on running #933

cor277 opened this issue Dec 24, 2023 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@cor277
Copy link

cor277 commented Dec 24, 2023

when try to run the gpt-engineer from docker I recieve this error :

docker run -it --rm -e OPENAI_API_KEY=sk-iv9R5S5u0XqSmTdR1JnOT3BlbkFJSxxxxxxxxx -v .:/project gpt-engineer
/app/entrypoint.sh: line 3: $'\r': command not found
unning gpt-engineer in /project

What application do you want gpt-engineer to generate?
^C <--------- i tstopped the run for error above.

@cor277 cor277 added bug Something isn't working triage Interesting but stale issue. Will be close if inactive for 3 more days after label added. labels Dec 24, 2023
@ATheorell ATheorell removed the triage Interesting but stale issue. Will be close if inactive for 3 more days after label added. label Dec 24, 2023
@arghhjayy
Copy link

arghhjayy commented Jan 17, 2024

Can't replicate this, maybe this is fixed?
Can you try again and check?
I'm using Windows 11, Docker Desktop v4.16.2 (95914)

@viborc
Copy link
Collaborator

viborc commented Jan 31, 2024

@cor277 does this issue still persist or you don't get that error anymore?

@oldmanjk
Copy link

oldmanjk commented Mar 4, 2024

I still get this error attempting to run from windows and wsl2. Also, does anyone know how to do "improve" from docker?

@k1lgor
Copy link
Contributor

k1lgor commented Mar 23, 2024

@cor277 @oldmanjk It seems that the entrypoint.sh file may have a CRLF end of the file, which could be causing the issue. To resolve this, try changing it to LF. In CRLF, every new line is marked by \n\r, but Unix does not recognize the \r character. Changing to LF should fix the problem.

@ATheorell
Copy link
Collaborator

Does @k1lgor s comment resolve this @oldmanjk @cor277 ? Can we close this or do we need changes to the codebase?

@oldmanjk
Copy link

oldmanjk commented Apr 4, 2024

Does @k1lgor s comment resolve this @oldmanjk @cor277 ? Can we close this or do we need changes to the codebase?

How do I implement this when I'm running stable? Also, if it works, wouldn't you need to change the codebase?

@viborc
Copy link
Collaborator

viborc commented May 4, 2024

@oldmanjk are you still experiencing this error? It's been a while since this issue was last active and if it's not relevant anymore, I'd like to close it.

Please, let us know.

@oldmanjk
Copy link

oldmanjk commented May 4, 2024

@oldmanjk are you still experiencing this error? It's been a while since this issue was last active and if it's not relevant anymore, I'd like to close it.

Please, let us know.

No one ever answered my question and I couldn't figure it out so I moved on. I don't know if it's still an issue. Good luck out there

@captivus
Copy link
Collaborator

captivus commented May 9, 2024

@zigabrencic will review in conjunction with #1136 and, pending resolution, will close.

@k1lgor
Copy link
Contributor

k1lgor commented May 17, 2024

Here is the replication of the error mentioned:
Open the entrypoint.sh file in VSCode and click at the bottom on the editor
image
and choose CRLF at the top. If you build the container now, will be successful, but executing the entrypoints.sh file inside the container wont be
image
because the shell does not recognize the CRLF ending of the line. This happens if you create files under Windows env.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants