-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Document how to use Python & Jupyter #4333
Comments
Great work @AyaanZaveri! This is fantastic. Thanks for taking the time to write this up. I've pinned it for now (until we can get around to adding this to the docs). This should be a guide in it of itself. |
Hi, Using this dockerfile FROM debian:buster-slim
ENV SHELL /bin/bash
# Install system dependencies
RUN apt-get update \
&& DEBIAN_FRONTEND=noninteractive apt-get install -y \
curl \
wget \
git \
screen \
unzip \
vim \
procps \
&& apt-get clean
ENV PATH=/opt/conda/bin:$PATH
RUN wget --quiet https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh \
&& /bin/bash Miniconda3-latest-Linux-x86_64.sh -f -b -p /opt/conda \
&& rm Miniconda3-latest-Linux-x86_64.sh \
&& conda install --quiet --yes jupyter
RUN curl -fsSL https://code-server.dev/install.sh | sh
RUN code-server --install-extension ms-python.python
RUN code-server --install-extension ms-toolsai.jupyter
WORKDIR /tmp
CMD code-server --bind-addr 0.0.0.0:8080 --auth=none /tmp
# docker build -t jupyter .
# docker run -p 8080:8080 -it --rm jupyter I'm unable to create a new blank notebook or run a pre-existing notebook. Here's the error trace in the output logs
There's an out/client_renderer/ dir but no out/client/ |
You can try removing the lines:
and install the Python extension manually (It should be bundled with the Jupyter Extension). |
Same result |
Can you try to use the exact same Dockerfile?
Does that work? |
Yes that does work but it's vscode 1.54 with the old notebooks |
@jsjoeio I finally got around to read your (great!) worklog in #3874 and I'm not sure we fixed the original root-cause, which is still what @0x0L is seeing here? As in, I think the problem you fixed with #4231 was a change on the API itself for the future versions of vscode (as it was the insider's version). The current root-cause still is that the
Unless moving to Open VSX (#4319) will indeed come with 3.12.1 (and even depending on the release date), there likely still is some work to do to ensure the extension vended in code-server's current gallery is complete... I would recommend to re-upload a working extension to code-server's VSX gallery, either by taking it from Open VSX or GitHub, or building it locally? I'm happy to provide a version that I'd build myself so you can upload it? @0x0L As per the matrix I created here the only working version of If you don't want to completely switch to Open VSX, I reckon the following should work in a Dockerfile - just to install the extensions?
|
Thanks @edvincent for your matrix. I used the extensions from the official market place as a temporary fix |
I'm hopeful we can make it happen with 3.12.1
That would save a lot of time and would be super appreciated 🙏 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days. |
If this doesn't work use the Dockerfile from #3199 (comment)
The text was updated successfully, but these errors were encountered: