René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How does it work?","acceptedAnswer":{"@type":"Answer","text":"At its core, each project's runtime environment is a Docker image, giving you extensive customization options. Anything you can define in a Dockerfile can be implemented in your Deepnote project. This is particularly powerful for:\n\nBuilding libraries from source with specific versions\nInstalling custom binary dependencies\nManaging Python packages through requirements.txt\n\nCustom environments are especially valuable for complex projects where dependency installation is time-consuming and needs to be reused across multiple notebooks."}},{"@type":"Question","name":"How to create a custom environment?","acceptedAnswer":{"@type":"Answer","text":"Local Dockerfile\n\nBuilding a local Dockerfile in Deepnote is a premium feature available only on Team and Enterprise plans.\n\nYou can customize your environment by placing a Dockerfile in your project's root directory. Deepnote handles all the image building and hosting for you.\n\nThe most common approach is to extend one of our default environments. For example, here's how to add OpenCV dependencies to our Python 3.11 base image:\n\nTo use your local Dockerfile, simply select Dockerfile from the Environment dropdown.\n\nThe Environment selection dialog with Dockerfile selected.\n\nWhen building from a local Dockerfile, only the following Docker instructions are supported:\n\nFROM: Start with any public base image or Deepnote environment\nRUN: Execute commands as root to install libraries and tools\nENV: Set environment variables or define default Jupyter kernels\n\nLocal Dockerfile builds are available on Team and Enterprise plans with the following constraints:\n\nMaximum build time: 60 minutes\nFor longer builds, we recommend building outside of Deepnote (see below)\n\nHosted docker image\n\nPublic images\n\nYou can use any publicly available Docker image from repositories like Docker Hub, giving you access to thousands of pre-configured environments.\n\nPrivate Repositories\n\nTeam and Enterprise users can connect to private image repositories from:\n\nDocker Hub\nGoogle Container Registry\nAmazon ECR\n\nTo use private repositories:\n\n1. Create an integration with your repository provider\n2. Add your credentials\n3. Connect the integration to projects where you need your private images\n\nThe Add Docker environment dialog with the Name and Docker image fields and private image provider guidance."}}]}