-
Notifications
You must be signed in to change notification settings - Fork 590
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
bug: devcontainer is missing GDAL #9011
Comments
|
@anentropic Thanks for reporting this. I'm not quite sure what's going on, because the geospatial dependencies were added recently, see #8837 and it looks like you are running on main. @cpcloud any idea what could be going on here? |
|
A local vs code environment a codespace are not the same. If a package attempting to call |
|
I don't think it's a local versus remote issue. I also don't really understand how this works. Does the codespace run on GitHub infrastructure and VS code just "points" at that? |
|
I don't think anyone's used the devcontainer setup locally, but it works on GitHub codespaces. I use it from time to time to try things that I don't want to run locally. |
|
I believe it's running a docker container locally on my machine from the terminal I get: which makes sense as I'm on an M2 macbook |
Not entirely sure whether this will be possible to deal with. Speculating here, but I think this is probably related to how volumes are being mounted inside the container. |
|
That error is also happening in I think we probably need someone who develops using a Mac to debug this |
|
for kicks I pasted in the traceback above and asked the new Llama 3 for a solution... it actually gave a nice explanation and something that worked (!) amending the update content script to: POETRY_DYNAMIC_VERSIONING=false python3 -m pip install -e '.[clickhouse,duckdb,clickhouse,examples,geospatial]'got around the dunamai issue So the two parts of the fix are probably:
FROM mcr.microsoft.com/vscode/devcontainers/python:3.11
RUN apt-get update && apt-get install -y --no-install-recommends libgdal-dev
|
|
Hey @anentropic -- want to give it another shot now and see if it works? |
## Description of changes These change are what was required for me to get the devcontainer to run on my machine. Before these changes, the devcontainer image wasn't building correctly because it was missing gdal. The root cause of that was that the devcontainer.json wasn't using the Dockerfile. - The previous devcontainer.json wasn't actually using the Dockerfile, now it does - In devcontainer.json, I switched updateContent command for postCreateCommand as that looks more appropriate based on the docs - A couple of minor tidying changes ## Issues closed Resolves #9011
Not working yet but looks like #9019 will fix it (needs the change in |
|
Just merged that, give it another go if you can! |
|
Apologies, but it seems I tried it and it appeared to work (i.e. by entering that line manually in terminal of a failed container launch) but it doesn't work when (re)building the container from scratch ...I tried again just now and same thing. (And I can't find evidence for it via Google or GitHub search) I'm not sure what devcontainers is doing to make the two scenarios behave differently According to poetry-dynamic-versioning plugin docs a correct env var to disable active versioning would be I tried this and took care to make devcontainers rebuild the image with it and it seems to work |
|
PR to fix the hallucination: #9031 |
What happened?
I checked out the repo and opened it in VS Code. It found a
.devcontainerconfig and prompted me to open in a container... I thought this might be easier than messing around with conda etcBut it doesn't work. The
updateContent.shscript fails trying to pip install dependencies with an error:Presumably gdal is not installed in the
mcr.microsoft.com/vscode/devcontainers/python:3.11base imageBy adding
"remoteUser": "vscode"to the devcontainer.json I was able tosudo apt-get install libgdal-devThis got further but hit another problem:
(this is running from the VS Code terminal window after opening the project as/in a devcontainer)
What version of ibis are you using?
git HEAD
4ad734dWhat backend(s) are you using, if any?
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: