Skip to content

fail to start jupyter server in kubernetes container #2330

Closed

Description

@tom-shan

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

similar issue in https://github.com/microsoft/vscode-python/issues/8661
if I follow these steps in https://github.com/microsoft/vscode-python/issues/8661#issuecomment-557202665, it works as expected.

Actual behavior

Jupyter notebook failed to launch. Error: Jupyter server crashed. Unable to connect. Error code from jupyter: 0 Failed to run jupyter as observable with args notebook --no-browser --notebook-dir=/tmp/11efa7e5-f7da-4094-8380-b337f76d0cf5 --NotebookApp.iopub_data_rate_limit=10000000000.0

Expected behavior

Your Jupyter and/or Python environment

Please provide as much info as you readily know

  • Jupyter server running: Local
  • Extension version: 2020.1.58038
  • Python and/or Anaconda version: 3.6.9
  • OS: Linux (ubuntu 18.04):
  • Virtual environment: N/A

Developer Tools Console Output

Microsoft Data Science for VS Code Engineering Team: Rich Chiodo (@rchiodo), Ian Huff (@IanMatthewHuff), David Kutugata (@DavidKutu), Don Jayamanne (@DonJayamanne), Jim Griesmer (@greazer)

Activity

  1. changed the title [-]fail to start jupyter runtime in k8s container[/-] [+]fail to start jupyter server in k8s container[/+] on Feb 7, 2020
  2. changed the title [-]fail to start jupyter server in k8s container[/-] [+]fail to start jupyter server in kubernetes container[/+] on Feb 7, 2020
  3. rchiodo commented on Feb 7, 2020

    @rchiodo
    Contributor

    Not sure if we can detect k8s or not (so we can add the correct command line arguments), but https://github.com/microsoft/vscode-python/issues/8698 would at least make it possible to set your own command line arguments.

  4. rchiodo commented on Feb 7, 2020

    @rchiodo
    Contributor

    Right now your PR won't show up until March (although you can use the insider's build)

    We're discussing whether or not we can take this into our upcoming release (today's the last day for submissions, so probably not)

  5. locked as resolved and limited conversation to collaborators on Feb 14, 2020
  6. unlocked this conversation on Nov 13, 2020
  7. locked as resolved and limited conversation to collaborators on May 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions