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
gitpod setup fails #3386
Comments
I was able to resolve this in gitpod by entering this into the shell: I think the default rust version is behind which is causing this error. I don't know enough about gitpod (or rust for that matter :S) to give any more of a comment on this 😂 |
I'm getting this same error when running |
Are you using this inside the gitpod for nushell @ijt ? |
I wasn't but then I took your suggestion and built it within gitpod, then
scp-ed it to my box. Now it's working for me. Thanks!
…On Wed, Jun 16, 2021 at 9:49 PM Alex ***@***.***> wrote:
Are you using this inside the gitpod for nushell @ijt
<https://github.com/ijt> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3386 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADZKRSJL4MSSRKWXCJCLDTTFWC7ANCNFSM44FNTFFA>
.
|
This issue is being marked stale because it has been open for 30 days without activity. If you feel that this is in error, please comment below and we will keep it marked as active. |
this is still an issue |
I think the issue here might be related with the fact that gitpod is not rebuilding the custom Docker image on prebuilds unless the Dockerfile is changed, which leads to the usage of an old image with an outdated rust version (looks like A way to solve this might be to make use of a gitpod |
this seems to be fixed:
|
The gitpod setup fails with
The error looks similar to #3282 which was solved by updating rust to 1.51
Default rust version for gitpod is 1.51 see https://github.com/gitpod-io/workspace-images/blob/master/full/Dockerfile#L196 so should be good?
(Also the README states you need rust 1.47 or later is this correct?)
The text was updated successfully, but these errors were encountered: