-
Notifications
You must be signed in to change notification settings - Fork 17
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
DevContainer: Exit code 137 #2
Comments
After adding these runArgs
in devcontainer.json the error messages changes to
|
Hi @Yumin-Sun-00 could you maybe try running Ctrl + Shift + P or Command + Shift + P on MacOS and type |
Hi @JenSeReal I provision a EC2 instance with Instance type And I remove my changes and have tried: Dev Containers: Rebuild and Reopen in Container Both returns with |
Maybe more system informarion of my EC2 instance might helpful?
|
Hi, I am not sure, if the problem originates from the memory config of your VM instance. Can you give some more details about your setup. I understood RHEL8. If you use the way Jens has described before, there also is an option "Dev Containers: Show container log" If the rebuild step from above did not work, you may want to try to delete the stopped container instance and image directly via docker commands and completely start from scratch. In general I am not sure if it makes a lot of sense to deploy a VM instance only for this purpose. Here is some general codespace documentation, if this is new for you: https://docs.github.com/en/codespaces |
Hi @maeddes ,
VS Code version: 1.95.2 (user setup) Dev Containers version: v0.388.0 Delete images and containers I have to keep everything clean before rebuild:
Now: In VS Code, reopen in containers --> exit code 137. Here is the logs: [1180 ms] Dev Containers 0.388.0 ov.txt Thanks for providing alternative. I will have a look now. |
I found in the logs there is another exit code 128 before exit code 137: fatal: detected dubious ownership in repository at '/workspaces/LFS148-code'
Do you think this could be the cause? |
I think it could be, but I can't verify (yet). We've never seen this issue and we can't reproduce it |
You could try to set the save directory in a startup command like this |
Hi @JenSeReal , I have tried different versions of such commands
None of them worked. I currently give up on this, and will try the codespaces as maeddes recommended. Thanks for your support, I am appreciated on that. |
thanks for the updates here. We were still unable to reproduce this behaviour on our end. If we get the chance, can you let us some details, about the VM and in particular the OS and settings. many thanks for patience here! |
Hi @maeddes I was also thinking about it is because of VM workstation, therefore at the beginning I provision a ec2 instance to try again. I think this is more related to Git new security features, that the owner of files must match to the user who perform git operations. I found in github there were/are issues/discussions about this new features, some solutions are proposed. But it seems like there are still people suffering from this. It sounds like it is about when .gitconfig will be copy pasted from host into the container. From this perspective, I think it is less relevant to VMs, though at the beginning I indeed had such idea, therefore you see I provisioned a new ec2 instance. I see 2 options to fix this, however I am not familiar with docker container.
I just roughly say out my opinions, but I do not know whether this is promising. BTW the codes pace things also not work by me, not sure whether it is because I am using my company laptop.... Have a good day! 🍻 |
You could also maybe try to download the repo as a zip file or to just delete the |
Hey, that is a good idea! I get rid of the exit code 128 now 🎶🤩🥳 However, it still not work 🥲😂😂😂😂😂😂😂😂 Here is the log...I am done with this, I have to move on. It is a nice tutorial though that I wish to have a look very long time. |
first of all thanks for providing all the feedback here. If we can resolve it we will reach out to you. Sorry we couldn't make it work yet |
I can not reopen folder to develop in a container.
Error message: An error occurred setting up the container.
My VM Workstation (Linux client):
Memory: 8GB
OS: RHEL8
The text was updated successfully, but these errors were encountered: