Skip to content

Latest commit

 

History

History
1363 lines (831 loc) · 48.3 KB

File metadata and controls

1363 lines (831 loc) · 48.3 KB

Setup instructions

Below are the instructions for setting up your computer for the Le Wagon Data Science & AI bootcamp.

Please read them carefully and execute all commands in the following order.

This setup is not an exercise; its sole purpose is to prepare your machine in a standardised way. Do not experiment or ask an LLM for help. If you get stuck, simply ask a teacher for help 🙋

Let's start 🚀

GitHub account

Have you signed up to GitHub? If not, do it right away.

👉 Upload a picture and put your name correctly on your GitHub account. This is important as we'll use an internal dashboard with your avatar. Please do this now, before you continue with this guide.

GitHub picture

👉 Enable Two-Factor Authentication (2FA). GitHub will send you text messages with a code when you try to log in. This is important for security and also will soon be required in order to contribute code on GitHub.

Windows version

Before we start, we need to check that the version of Windows installed on your computer is compatible with this setup instructions.

Windows 10 or Windows 11

⚠️ Note on Windows 10 and security

The Le Wagon bootcamp setup works on Windows 10. That said, we highly recommend to upgrade to Windows 11. Since October 14th, 2025, Microsoft has ended support for Windows 10, which means it will no longer receive security updates, potentially putting your machine at risk. For more details, read Microsoft's guide. In case your machine can't run Windows 11, consider switching to Ubuntu.

To be able to set up your computer, you need to have Windows 10 or Windows 11 installed.

To check your Windows version:

  • Press Windows + R
  • Type winver
  • Press Enter

✔️ If the first words of this window are Windows 11 you're good to go 👍

If the first words of this window are Windows 10, check the Version number:

  • ✔️ If it says at least 2004, you are good to go 👍

  • ❌ If it is below 2004, you need to run an update.

  • How to install updates?

    Open Windows Update:

    • Press Windows + R
    • Type ms-settings:windowsupdate
    • Press Enter
    • Click on Check updates

    ✔️ If you see a green check mark and the message "You're up to date", you're good to go 👍

    ⚠️ If you have a red exclamation mark and the message "Update available", please install them and repeat the process until it says that you are up to date ➿

    ❌ If you have an error message about Windows not being able to apply updates, please contact a teacher.

    Activate Windows Update Service to fix Updates

    Some antiviruses and pieces of software deactivate the Update service we need, resulting in the error you see. Let's fix that!

    • Press Windows + R
    • Type services.msc
    • Press Enter
    • Double Click Windows Update Service
    • Set its Startup to Automatic
    • Click on Start
    • Click on Ok Then let's try updates again!

    Check the version number again:

    • Press Windows + R
    • Type winver
    • Press Enter

    ✔️ If it says at least 2004, you are good to go 👍

    ❌ If it is below 2004, contact a TA.

Virtualization

We need to ensure that the Virtualization options are enabled in the BIOS of your computer.

For many computers, this is already the case. Let's check:

  • Press Windows + R
  • Type taskmgr
  • Press Enter
  • Click on the Performance tab
  • Click on CPU

Windows task manager

✔️ If you see "Virtualization: Enabled", you're good to go 👍

❌ If the line is missing or if the virtualization is disabled, please contact a teacher before trying to activate the Virtualization

Activate Virtualization

We need to access the BIOS / UEFI of the computer to activate it.

  • Press Windows + R
  • Type shutdown.exe /r /o /t 1
  • Press Enter
  • Wait for the computer to shutdown
  • Click on Troubleshoot
  • Click on Advanced Options
  • Click on UEFI Firmware Settings
  • Click on Restart

You need to activate the virtualization option for your processor here:

  • Most of the time, in the advanced settings, the CPU settings, or the Northbridge settings
  • The option can be called differently according to your computer:
    • Intel: Intel VT-x, Intel Virtualization Technology, Virtualization Extensions, Vanderpool...
    • AMD: SVM Mode or AMD-V
  • Save the changes after activation and reboot the computer through the appropriate option

Windows Subsystem for Linux (WSL)

WSL is the development environment we are using to run Ubuntu. You can learn more about WSL here.

We will install WSL 2 and Ubuntu in one command through the Windows Command Prompt.

⚠️ In the following instruction, please be aware of the Ctrl + Shift + Enter key stroke to execute Windows Command Prompt with administrator privileges instead of just clicking on Okor pressing Enter.

  • Press Windows + R
  • Type cmd
  • Press Ctrl + Shift + Enter

⚠️ You may have to accept the UAC confirmation about the privilege elevation.

A black terminal window will appear:

  • Copy the following command (Ctrl + C)
  • Paste it into the terminal window (Ctrl + V or by right-clicking in the window)
  • Run it by pressing Enter
wsl --install

✔️ If the command ran without any error, please restart your computer and continue below 👍

❌ If you encounter an error message (or if you see some text in red in the window), please contact a teacher.

Troubleshooting for Windows 10 (only if needed, check with a TA)

For Windows 10 < 2004: install WSL 1 first

⚠️ In the following instruction, please be aware of the Ctrl + Shift + Enter key stroke to execute Windows PowerShell with administrator privileges instead of just clicking on Okor pressing Enter.

  • Press Windows + R
  • Type powershell
  • Press Ctrl + Shift + Enter

⚠️ You may have to accept the UAC confirmation about the privilege elevation.

A blue terminal window will appear:

  • Copy the following commands one by one (Ctrl + C)
  • Paste them into the PowerShell window (Ctrl + V or by right-clicking in the window)
  • Run them by pressing Enter
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

✔️ If all three commands ran without any error, please restart your computer and continue below 👍

❌ If you encounter an error message (or if you see some text in red in the window), please contact a teacher

For Windows 10 users running WSL 1: Upgrade to WSL 2

If you are running Windows 10, we will then upgrade WSL to version 2.

Once your computer has restarted, we need to download the WSL2 installer.

  • Go to the download page
  • Download "WSL2 Linux kernel update package"
  • Open the file you've just downloaded
  • Click Next
  • Click Finish

Update WSL from version 1 to 2

✔️ If didn't encounter any error message, you're good to go 👍

❌ If you encounter the error "This update only applies to machines with the Windows Subsystem for Linux", right click on the program and select uninstall; you shall be able to install it normally this time.

For Windows 10 users running WSL 1: Make WSL 2 the default Windows Subsystem for Linux

If you are running Windows 10, we will set WSL default version to 2.

Now that WSL 2 is installed, let's make it the default version:

  • Press Windows + R
  • Type cmd
  • Press Enter

In the window which appears, type:

wsl --set-default-version 2

✔️ If you see "The operation completed successfully", you can close this terminal and continue to follow the instructions below 👍

❌ If the message you get is about Virtualization, please contact a teacher

Enable Virtual Machine Platform Windows feature

Follow the steps described here until you enable Virtual Machine Platform and Windows Subsystem for Linux

Enable Hyper-V Windows feature

Follow the steps described here until you enable the group Hyper-V

ℹ️ If you are running Windows 10 Home edition, Hyper-V feature is not available for your operating system. It's non-blocking and you can still continue to follow the instructions below 👌

Ubuntu

Installation

After restarting you computer, you should see a terminal window saying WSL is resuming the Ubuntu installation process. When it's done, Ubuntu will be launched.

Troubleshooting for Windows 10 (only if needed, check with a TA)

If the Ubuntu installation did not resume, first try it again: launch Powershell or the Command Prompt again and run wsl --install again.

If you are running Windows 10, let's install Ubuntu throught the Microsoft Store:

  • Click on Start
  • Type Microsoft Store
  • Click on Microsoft Store in the list
  • Search for Ubuntu in the search bar
  • Select version without any number, just plain "Ubuntu"
  • Click on Get

⚠️ Don't install Ubuntu 18.04 LTS nor Ubuntu 20.04!

Uninstall wrong versions of Ubuntu

To uninstall a wrong version of Ubuntu, you just have to go to the Installed Program List of Windows 10:

  • Press Windows + R
  • Type ms-settings:appsfeatures
  • Press Enter

Find the software to uninstall and click on the uninstall button.

Once the installation is finished, the Get button becomes a Open button: click on it.

First launch

At first launch, you will be asked some information:

  • Choose a username:
    • one word
    • lowercase
    • no special characters
    • for example: lewagon or your firstname
  • Choose a password
  • Confirm your password

⚠️ When you type your password, nothing will show up on the screen, that's normal. This is a security feature to mask not only your password as a whole but also its length. Just type your password and when you're done, press Enter.

Check your username

Type this in the Ubuntu terminal:

whoami

It should return the username you chose before.

❌ It if says root, contact a TA before continuing!

Visual Studio Code

Installation

Let's install Visual Studio Code text editor.

VS Code installation options

When the installation is finished, launch VS Code.

Connecting VS Code to Ubuntu

To make VS Code interact properly with Ubuntu, let's install the Remote - WSL VS Code extension.

Open your Ubuntu terminal.

Copy-paste the following commands in the terminal:

code --install-extension ms-vscode-remote.remote-wsl

Then open VS Code from your terminal:

code .

✔️ If you see WSL: Ubuntu in the bottom left corner of the VS Code window, you're good to go 👍

WSL Ubuntu Remote

❌ Otherwise, please contact a teacher

Windows Terminal

Installation

ℹ️ The following instructions depend on your version of Windows.

If you are running Windows 11, the Windows Terminal is already installed and you can proceed to the next section 👇

If you are running Windows 10, let's install Windows Terminal, a real modern terminal.

Windows 10: Install Windows Terminal
  • Click on Start
  • Type Microsoft Store
  • Click on Microsoft Store in the list
  • Search for Windows Terminal in the search bar
  • Select Windows Terminal"
  • Click on Install

⚠️ DO NOT install Windows Terminal Preview, just Windows Terminal!

Uninstall wrong version of Windows Terminal

To uninstall a wrong version of Windows Terminal, you just have to go to the Installed Program List of Windows 10:

  • Press Windows + R
  • Type ms-settings:appsfeatures
  • Press Enter

Find the software to uninstall and click on the uninstall button.

Once the installation is finished, the Install button becomes a Launch button: click on it.

Ubuntu as the default terminal

Let's make Ubuntu the default terminal of your Windows Terminal application.

Press Ctrl + ,

It should open the terminal settings:

Windows Terminal Settings

  • Change the default profile to "Ubuntu"
  • Click on "Save"
  • Click on "Open JSON file"

You may see an orange circle rather than a penguin as the logo for Ubuntu.

We have circled in red the part you need to add:

Windows Terminal JSON settings file

First, let's ask Ubuntu to start directly inside your Ubuntu Home Directory instead of the Windows one.

  • Place this line inside the { } block that contains "name": "Ubuntu" (like in the screenshot):
"commandline": "wsl.exe ~",

⚠️ Do not forget the comma at the end of the line!

Then, let's disable warnings for copy-pasting commands between Windows and Ubuntu:

  • Locate the line "defaultProfile": "{2c4de342-...}"
  • Add the following line after it:
"warning.multiLinePaste": false,

⚠️ Do not forget the comma at the end of the line!

You can save these changes by pressing Ctrl + S

✔️ Your Windows Terminal is now setup 👍

This terminal has tabs: you can choose to open a new terminal tab by clicking on the + next to the current one.

From now on, every time we will refer to the terminal or the console it will be this one. DO NOT use any other terminal anymore.

VS Code Extensions

Installation

Let's install some useful extensions to VS Code.

code --install-extension ms-vscode.sublime-keybindings
code --install-extension emmanuelbeziat.vscode-great-icons
code --install-extension MS-vsliveshare.vsliveshare
code --install-extension ms-python.python
code --install-extension KevinRose.vsc-python-indent
code --install-extension ms-python.vscode-pylance
code --install-extension ms-toolsai.jupyter
code --install-extension alexcvzz.vscode-sqlite

Here is a list of the extensions you are installing:

VS Code AI Features

VS Code includes many powerful AI features, which are a great tool once you already know how to code.

That said, relying on AI too early can hide important concepts and make debugging harder to understand. Once you’re comfortable with the fundamentals, you’ll know when and how to use AI effectively — without letting it do the thinking for you.

For the start of the bootcamp, we’ll disable these features. At the right point in the course, we’ll reenable them so you can put them to good use.

In VS Code:

  1. Let's open the VS Code "Command Palette": type Ctrl-Shift-P.
  2. This will open the Command Palette: a small text box at the top of your screen. Start typing aifeatures until you see "Chat: Learn How to Hide AI features". Click on it. The Command Palette at the top of the screen
  3. This will open the settings, and will show you the option "Disable and hide built-in AI features ...". Tick the checkbox in front of that option. Check the disable option

Later, if you want to reenable the AI features, you can follow the same instructions to untick the checkbox.

Command line tools

Check the locale

The locale is a mechanism allowing to customize programs to your language and country.

Let's verify that the default locale is set to English, please type this in the Ubuntu terminal:

locale

If the output does not contain LANG=en_US.UTF-8, run the following command in a Ubuntu terminal to install the english locale:

sudo locale-gen en_US.UTF-8

If after, you receive a warning (bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf-8)) in your terminal, please do the following:

Generate locale

Please, run this lines in your terminal.

sudo update-locale LANG=en_US.UTF8
sudo apt-get update
sudo apt-get install language-pack-en language-pack-en-base manpages

Zsh & Git

Instead of using the default bash shell, we will use zsh.

We will also use git, a command line software used for version control.

Let's install them, along with other useful tools:

  • Open an Ubuntu terminal
  • Copy and paste the following commands:
sudo apt update
sudo apt install -y curl git imagemagick jq unzip vim zsh tree direnv

These commands will ask for your password: type it in.

⚠️ When you type your password, nothing will show up on the screen, that's normal. This is a security feature to mask not only your password as a whole but also its length. Just type in your password and when you're done, press Enter.

GitHub CLI installation

Let's now install GitHub official CLI (Command Line Interface). It's a software used to interact with your GitHub account via the command line.

In your terminal, copy-paste the following commands and type in your password if asked:

sudo apt remove -y gitsome # gh command can conflict with gitsome if already installed
curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo dd of=/usr/share/keyrings/githubcli-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null
sudo apt update
sudo apt install -y gh

To check that gh has been successfully installed on your machine, you can run:

gh --version

✔️ If you see gh version X.Y.Z (YYYY-MM-DD), you're good to go 👍

❌ Otherwise, please contact a teacher

Oh-my-zsh

Let's install the zsh plugin Oh My Zsh.

In a terminal execute the following command:

sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

If asked "Do you want to change your default shell to zsh?", press Y

At the end your terminal should look like this:

Ubuntu terminal with OhMyZsh

✔️ If it does, you can continue 👍

❌ Otherwise, please ask for a teacher

Linking your default browser to Ubuntu

To be sure that you can interact with your browser installed on Windows from your Ubuntu terminal, we need to set it as your default browser there.

Run the following command and follow the instructions. The tool will prompt you to choose one of the browsers that are available on your system. You just need to type in the number that is shown in front of the browser.

bash -c "$(curl -s https://raw.githubusercontent.com/julesvanrie/wslsetbrowser/refs/heads/main/wslsetbrowser.sh)"

Reset your terminal:

exec zsh

GitHub CLI

CLI is the acronym of Command-line Interface.

In this section, we will use GitHub CLI to interact with GitHub directly from the terminal.

It should already be installed on your computer from the previous commands.

We will use the GitHub CLI (gh) to connect to GitHub using SSH, a protocol to log in using SSH keys instead of the well known username/password pair.

First in order to login, copy-paste the following command in your terminal:

⚠️ DO NOT edit the email — Even though user:email looks like a placeholder for your actual email address, it isn't — do not replace it.

gh auth login -s 'user:email' -w --git-protocol ssh

gh will ask you few questions:

  • Generate a new SSH key to add to your GitHub account? Press Enter to ask gh to generate the SSH keys for you.

    If you already have SSH keys, you will see instead Upload your SSH public key to your GitHub account? With the arrows, select your public key file path and press Enter.

  • Enter a passphrase for your new SSH key (Optional):

    • FOR MOST PEOPLE: Just press Enter to skip. You don't need a passphrase for the bootcamp and it would prompt you every time you use the key. There is a risk, however, that if someone steals your laptop, they could then push to GitHub.
    • IF SECURITY IS REALLY IMPORTANT TO YOU: Enter a passphrase of your choice and press Enter. It's really important that if you enter a passphrase, you write it down somewhere immediately and do not lose/forget it. You will need to enter this frequently.
  • Title for your SSH key. You can leave it at the proposed "GitHub CLI", press Enter.

You will then get the following output:

! First copy your one-time code: 0EF9-D015
- Press Enter to open github.com in your browser...

Select and copy the code (0EF9-D015 in the example), then press Enter.

Your browser will open and ask you to authorize GitHub CLI to use your GitHub account. Accept and wait a bit.

Come back to the terminal, press Enter again, and that's it.

To check that you are properly connected, type:

gh auth status

✔️ If you get Logged in to github.com as <YOUR USERNAME> , then all good 👍

❌ If not, contact a teacher.

Dotfiles

Let's enhance the experience of your machine by installing Le Wagon's pre-configured dotfiles 🔗. These are configuration files for your terminal, zsh, git, and VS Code.

Get your GitHub username

Run the following command:

export GITHUB_USERNAME=`gh api user | jq -r '.login'`
echo $GITHUB_USERNAME

✔️ You should see your Github username printed.

❌ If not, stop here and ask for help. There may be a problem with the previous step (gh auth).

Forking the dotfiles

To customise this configuration for yourself, you'll need to fork the repository to your own Github account.

Forking creates a copy of the repository under your account (your_github_username/dotfiles), which you can then modify with your personal information, such as your name.

❗ If you already did another Le Wagon bootcamp (Web Development, AI Software Development, Data Analytics, Data Science & AI, open a ticket with a TA and open this for instructions ❗

You may have an older version of the Le Wagon dotfiles. They could be incompatible with the current setup.

Together with a TA, do one of the following:

I'm using the same machine (or a new machine which already has the dotfiles).
  1. Move into your existing dotfiles folder:

    cd ~/code/$GITHUB_USERNAME/dotfiles
  2. Check the diff against the current version of Le Wagon's dotfiles:

    git diff upstream/master

If there is no meaningful difference other than your name and email setting, continue with the setup.

I'm using a new machine without the dotfiles.
  1. Browse to GitHub and find your dotfiles repository.

  2. Check how many commits it's behind and ahead lewagon/dotfiles:master. You can see this just above the file list.

  3. Click through to the behind and the ahead, and scroll down to see the diffs.

If there is no meaningful difference other than your name and email setting, continue with the setup.

The previous step revealed meaningful differences.

If you are OK with losing your existing dotfiles (recommended):

Be aware that this will remove any personal changes you made to your shell configuration, like loading extra utilites, or changing the look and feel of your shell. If you're not aware of any changes you made yourself, this should be fine.

  1. Delete your existing dotfiles repository on GitHub.
  2. Delete the local repository:
    cd ~/code && rm -rf ~/code/$GITHUB_USERNAME/dotfiles
  3. Continue with the setup.
If you do not want to lose your existing dotfiles, we recommend working with branches. Click to open.

On your laptop, or wherever you have a local copy of your existing version of dotfiles.

  1. Commit your current version of your dotfiles:

    git add .
    git status # Check what will be committed
    git commit -m "Version prior to new setup"
  2. Create a branch of your current dotfiles setup, and push to GitHub:

    git checkout -b old-setup
    git push origin old-setup
  3. Go back to master: git checkout master.

  4. On local master, git pull upstream master.

  5. Check that you're not in MERGING state. If you are, resolve any conflicts.

    It is important that you accept incoming changes to the .zshrc, .zprofile, and settings.json files. Especially anything related to pyenv and to Python environments.

    If there are too many conficts, use your code editor to replace the contents of the conflicting files with the ones from the Le Wagon dotfiles.

    Commit your conflict resolution: git commit --no-edit

  6. Push your changes to GitHub: git push origin master.

  7. Continue with the setup.


Time to fork the repo and clone it on your computer:

mkdir -p ~/code/$GITHUB_USERNAME && cd $_
gh repo fork lewagon/dotfiles --clone

If you're asked "Are you sure you want to continue connecting (yes/no/[fingerprint])?", type yes followed by Enter.

Installing the dotfiles

Run the dotfiles installer with:

cd ~/code/$GITHUB_USERNAME/dotfiles && zsh install.sh

Check the emails registered with your GitHub Account. You'll need to pick one in the next step:

gh api user/emails | jq -r '.[].email'

Run the git installer:

cd ~/code/$GITHUB_USERNAME/dotfiles && zsh git_setup.sh

☝️ This will prompt you for your name (FirstName LastName) and your email.

⚠️ You need to put one of the emails listed above from the previous gh api ... command. If you don't do that, Kitt will not be able to track your progress.

💡 Select the ...@users.noreply.github.com address if you don't want your email to appear in public repositories you may contribute to.

Install Python and dependencies

Your operating system - macOS, or Ubuntu (native, or inside WSL) - comes with a "system Python". That's a Python version your system depends on. We don't mess around with that one. We're going to do a professional setup of Python where you don't mess up your "system Python" and where you'll be able to switch which version you want to use for each project you work on.

To manage different Python versions and virtual environments (you'll discover what that means during the setup lecture), we will use the state-of-the-art uv created by Astral.

Install uv

First, we'll install uv:

curl -LsSf https://astral.sh/uv/install.sh | sh

Next, restart your shell by running this:

exec zsh

Create a virtual environment

Next, we'll create a virtual environment (an isolated environment with Python and the dependencies for the bootcamp):

uv venv ~/.lewagon/venvs/lewagon --python 3.12.9

Now that we created this new virtual environment, let's restart our shell to pick it up (this works thanks to the lewagon/dotfiles we installed before):

exec zsh

Let's check that everything went right. Run this:

which python3

It should return this:

/home/your-username/.lewagon/venvs/lewagon/bin/python3

If it doesn't, check with a TA! Do not continue with the next step before you solved this!

Install dependencies

Python is great for data, because the community has developed an enormous amount of packages we can re-use.

Let's install the most common ones:

uv pip install -r https://raw.githubusercontent.com/lewagon/data-setup/master/specs/releases/linux.txt

Jupyter Notebook tweaking

Depending on your system, we need to make some small changes to your Jupyter configuration.

Run this:

bash -c "$(curl -s https://raw.githubusercontent.com/lewagon/data-setup/refs/heads/master/checks/setup_jupyter.sh)"
If you are curious about what happens here, click here.

This script adds a configuration to improve the display of the details disclosure elements in your notebooks.

If you're using Windows WSL, it also fixes some other problems.

  • It makes sure your browser is configured correctly. It was configured before, but was overwritten by the dotfiles setup.
  • It fixes a known bug with Jupyter Notebook always opening the directory tree, even if you specify a specific file path.

Python setup check

Let's run some checks. If any of the following steps fail, ask a TA for help.

Let's reset your terminal:

cd ~/code && exec zsh

Make sure you can run Jupyter:

jupyter notebook

Your web browser should open on a jupyter window.

Note if you're running the setup on a virtual machine

VSCode detects that a jupyter notebook started in your virtual machine and creates a port forward in order to allow you to open the application in your browser.

Hit Open in Browser or go to http://localhost:8888/ (the url to use is available in the terminal).

On the first run, jupyter will ask for the token displayed in the terminal of your virtual machine in order to allow you to connect to the application from your local machine.

Fill the token and hit Log in.

You are now interacting from your local machine with the jupyter application running in your virtual machine.

jupyter.png

Click on New and in the dropdown menu select Python 3 (ipykernel):

jupyter_new.png

A tab should open on a new notebook:

jupyter_notebook.png

Make sure that you are running the correct python version in the notebook. Open a cell and run:

import sys; sys.version

It should output 3.12.9 followed by some more details. If not, check with a TA.

In another cell, run:

import pandas as pd
pd.__version__

This might take a few minutes to run. It should output a version number, 2.2.3. If not, check with a TA.

You can close your web browser then terminate the jupyter server with CTRL + C.

Here you have it! A complete python virtual env with all the third-party packages you'll need for the whole bootcamp.

Docker 🐋

Docker is an open platform for developing, shipping, and running applications.

if you already have Docker installed on your machine please update with the latest version

Install Docker

Go to Install Docker Desktop on Windows.

Download and install Docker Desktop.

If you have an Intel or AMD processor, choose the first option ending with "x86_64".

Not sure which processor you have?

Most probably you'll need the x86_64version, that is if you have an Intel or AMD processor.

If you don't know which processor your machine has, run arch in your Ubuntu terminal. Check its output:

  • x86_64: choose the first option "x86_64"
  • aarch64: choose the second option "Arm"

Once done, start Docker.

You should be able to run in a Ubuntu terminal:

docker run hello-world

The following message should print:

Permission denied?

Run the following commands one by one:

sudo groupadd docker
sudo usermod -aG docker $USER
newgrp docker

Try docker run hello-world again.

Seeing this error?

WARNING: Error loading config file: /home/user/.docker/config.json - stat /home/user/.docker/config.json: permission denied`?

Run the following command:

sudo rm -rf ~/.docker/

Try docker run hello-world again.

Google Cloud Platform setup

Google Cloud is a cloud solution that you are going to use in order to deploy your Machine Learning-based products to production.

🚨 If you are a student of the Part-Time Bootcamp or the Flex bootcamp, SKIP THIS SECTION FOR NOW! Google Cloud offers $300 worth of free credits for a duration of 3 months. You do not want to activate your Google Cloud account too soon 🙅‍♂️

Project setup

  • Go to Google Cloud and create an account if you do not already have one
  • In the Cloud Console, on the project list, select or create a Cloud project

⚠️ Important: When creating a new project, you will see an Organization field. Leave this set to "No organization". Do not select or create an organization. Choosing an organization applies restrictions that can prevent you from using Google Cloud services during the bootcamp.

  • Give it a name such as Wagon Bootcamp for example
  • Notice the ID automatically created for the project, e.g. wagon-bootcamp-123456

ℹ️ Note the Project ID (e.g. wagon-bootcamp-123456) this is not the same as the project name you chose (e.g. Wagon Bootcamp). You will need the ID later when running terminal commands, but don't worry, you can always find it in Google Cloud.

Account language

In order to facilitate the following of the instructions during the bootcamp, open your Google Cloud account preferences:

https://myaccount.google.com/language

If the preferred language is not:

  • English
  • United States

Then switch the language to english:

  • Click on the edit pen logo
  • Select English
  • Select United States
  • Click on Select

Billing account

You will now link your account to your credit card. This step is required or you will not be able to use the services provided by Google Cloud. Do not worry, you will be able to consume most Google Cloud services through free credits throughout the bootcamp.

⚠️ In some cases, Google may charge your card (around €10) to verify that it is valid. This will unfortunately not be refunded once you are approved, but will be added as credit in Google Cloud that you can use once your free credits have been used or expired.

  • Click on Billing
  • Click on MANAGE BILLING ACCOUNTS
  • Click on ADD BILLING ACCOUNT
  • Give a name to your billing account, e.g. My Billing Account
  • Click on "I have read..." and agree to the terms of service
  • Click on CONTINUE
  • Select your account type: Individual
  • Fill your name and address

You should see that you have a free credit of "$300 credits over the next 90 days".

  • Click on card details
  • Enter your credit card info
  • Click on START MY FREE TRIAL

Once this is done, verify that your billing account is linked to your Google Cloud project.

  • Select your project
  • Go to Billing
  • Select LINK A BILLING ACCOUNT
  • Select My Billing Account
  • Click on SET ACCOUNT

You should now see:

Free trial status: $300 credit and 91 days remaining - with a full account, you'll get unlimited access to all of Google Cloud Platform.
👉 If you do not own a credit card 👈

If you do not own a credit card, an alternative is to setup a Revolut account. Revolut is a financial app that will allow you to create a virtual credit card linked to your mobile phone billing account.

Skip this step if you own a credit card and use your credit card for the setup.

Download the Revolut app, or go to revolut and follow the steps to download the app (enter your mobile phone number and click on Get Started).

  • Open the Revolut app
  • Enter your mobile phone number
  • Enter the verification code received by SMS
  • The app will ask for your country, address, first and last name, date of birth, email address
  • The app will also ask for a selfie and request your profession
  • The app will require a photo of your identification card or passport

Once this is done, select the standard (free) plan. No need to add the card to Apple pay, or ask for a the delivery of a physical card, or add money securely.

You now have a virtual card which we will use for the Google Cloud setup.

In the main view of the Revolut app

  • Click on Ready to use
  • Click on the card
  • Click on Show card details
  • Note down the references of the virtual credit card and use them in order to proceed with the Google Cloud setup
👉 If you receive an email from Google saying "Urgent: your billing account XXXXXX-XXXXXX-XXXXXX has been suspended" 👈

This may happen especially in case you just setup a Revolut account.

  • Click on PROCEED TO VERIFICATION
  • You will be asked to send a picture of your credit card (only the last 4 digits, no other info)
  • In case you used Revolut, you can send a screenshot of your virtual credit card (do not forget to remove the validity date from the screenshot)
  • Explain that you are attending the Le Wagon bootcamp, do not own a credit card, and have just created a Revolut account in order to setup Google Cloud for the bootcamp using a virtual credit card

You may receive a validation or requests for more information within 30 minutes.

Once the verification goes through, you should receive an email stating that "Your Google Cloud Platform billing account XXXXXX-XXXXXX-XXXXXX has been fully reinstated and is ready to use.".

Enabling Google Cloud services

  • Make sure that billing is enabled for your Google Cloud project

ℹ️ You have a $300 credit to use for Google Cloud resources, which will be more than enough for the bootcamp.

That's it for the browser setup! Terminal setup comes later in this guide.

Google Cloud CLI

Install gcloud

Install the gcloud CLI to communicate with Google Cloud Platform through your terminal:

sudo apt-get update && sudo apt-get install ca-certificates gnupg curl
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo gpg --dearmor -o /usr/share/keyrings/cloud.google.gpg
echo "deb [signed-by=/usr/share/keyrings/cloud.google.gpg] https://packages.cloud.google.com/apt cloud-sdk main" | sudo tee -a /etc/apt/sources.list.d/google-cloud-sdk.list
sudo apt-get update && sudo apt-get install google-cloud-cli

👉 Install documentation

Configure the Google Cloud CLI

  • Authenticate the gcloud CLI with the google account you used for GCP

    gcloud auth login
  • Login to your Google account on the new tab opened in your web browser

  • List your active account and check your email address you used for GCP is present

    gcloud auth list
  • Set your current project (replace PROJECT_ID with the ID of your project, e.g. wagon-bootcamp-123456)

    gcloud config set project PROJECT_ID
  • List your active account and current project and check your project is present

    gcloud config list
  • Now let's set up Application Default Credentials so your Python code can access GCP:

    gcloud auth application-default login

    This will open a browser window. Log in with the same Google account you used to create your GCP project. Your credentials will be saved automatically.

  • Let's verify your Application Default Credentials are working:

    gcloud auth application-default print-access-token

    You should see a long token string. If you see an error, run gcloud auth application-default login again.

    Troubleshooting

🏁 You are done with the GCP setup!

Kitt

You should have received an email from Le Wagon inviting you to sign up on Kitt (our learning platform).

Then you should receive an additional invitation from Slack, inviting you to the Le Wagon Alumni slack community (where you'll chat with your buddies and all the previous alumni). Click on Join and complete the information.

If you haven't, please contact your teaching team.

Slack

Slack is a communication platform pretty popular in the tech industry.

Installation

Download the Slack app and install it.

⚠️ If you are already using Slack in your browser, please download and install the desktop app which is fully featured.

Settings

Launch the app and sign in to lewagon-alumni organization.

Make sure you upload a profile picture 👇

How to upload a profile picture on Slack

The idea is that you'll have Slack open all day, so that you can share useful links / ask for help / decide where to go to lunch / etc.

To ensure that everything is working fine for video calls, let's test your camera and microphone:

  • Open the Slack app
  • Click your profile picture in the top right.
  • Select Preferences from the menu.
  • Click Audio & video in the left-side column.
  • Below Troubleshooting, click Run an audio, video and screensharing test. The test will open in a new window.
  • Check that your preferred speaker, microphone and camera devices appear in the drop-down menus, then click Start test.

Check microphone and webcam with Slack

✔️ When the test is finished, you should see green "Succeed" messages at least for your microphone and camera. 👍

❌ If not, contact a teacher.

You can also install Slack app on your phone and sign in lewagon-alumni!

Windows settings

Exchange files between Windows and Ubuntu

We need an easy way to transfer files from Windows to Ubuntu and vice versa.

In order to do that, let's create shortcuts to Ubuntu directories in the Windows File Explorer:

  • Open the Windows File Explorer (or use the shortcut WIN + E)
  • In the Address Bar, enter \\wsl$\ (or \\wsl$\Ubuntu if it does not work)
  • You now have acces to the Ubuntu file system
  • Dive into the Ubuntu file system in order to look for directories of interest
  • Drag the desired folders into the Address Bar in order to create shortcuts

How to add a shortcut to Ubuntu file system on Windows

Open the Windows File Explorer from the Ubuntu terminal

Another option to move files around is to open the Windows File Explorer from the Ubuntu terminal:

  • Open an Ubuntu terminal
  • Go to the directory you wish to explore
  • Run the explorer.exe . command (alternatively, use wslview .)
  • If you get an input output error message, run wsl --shutdown in a Windows PowerShell and reopen an Ubuntu terminal

How to launch Windows Explorer from Ubuntu terminal

Find your way in the Ubuntu File System

You might want to figure out the exact location of a Windows directory in the Ubuntu file system, or the other way around.

In order to convert a Windows path to and from an Ubuntu path:

  • Open an Ubuntu terminal
  • Use the wslpath "C:\Program Files" command in order to translate a Windows path into an Ubuntu path
  • Use the wslpath -w "/home" command in order to translate an Ubuntu path into a Windows path
  • In particular, the wslpath -w $(pwd) command returns the Windows path of the current Ubuntu directory

How to access a Windows path from Ubuntu terminal

Pin apps to your taskbar

You are going to use most of the apps you've installed today really often. Let's pin them to your taskbar so that they are just one click away!

To pin an app to your taskbar, launch the app, right-click on the icon in the taskbar to bring up the context menu and choose "Pin to taskbar".

How to pin an app to the taskbar in Windows

You must pin:

  • Your terminal
  • Your file explorer
  • VS Code
  • Your Internet browser
  • Slack

(Bonus) Kata

If you are done with your setup, please ask around if some classmates need some help with theirs (macOS, Linux, Windows). We will have our first lectures at 2pm and will talk about the Setup you just did + onboard you on Kitt.

If you don't have a lot of experience with git and GitHub, please (re-)watch this workshop (1.25 playback speed is fine).

If you do, then you can wait for the first lecture working on this Tic-Tac-Toe Kata