diff --git a/Dockerfile b/Dockerfile
index c8ef05343e58b8..e105313756022c 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -7,8 +7,9 @@ ENV PATH="/root/.pyenv/bin:/root/.pyenv/shims:${PATH}"
 RUN pyenv install 3.7.3
 RUN pyenv global 3.7.3
 RUN pyenv rehash
-RUN pip3 install pyyaml==5.1.2 Cython==0.29.14 scons==3.1.1 pycapnp==0.6.4 Jinja2==2.10.3
 
+COPY requirements.txt /tmp/
+RUN pip install -r /tmp/requirements.txt
 
 ENV PYTHONPATH=/project
 
diff --git a/README.md b/README.md
index eec42dfefa7ff2..c11cf3fdcf5184 100644
--- a/README.md
+++ b/README.md
@@ -42,7 +42,7 @@ For example:
     SG_ VEHICLE_SPEED : 7|15@0+ (0.01,0) [0|250] "kph" PCM
     ```
 
-- Signal's size: always use the smallest amount of bits possible. For example, let's say I'm reverse engineering the gas pedal position and I've determined that it's in a 3 bytes message. For 0% pedal position I read a message value of `0x00 0x00 0x00`, while for 100% of pedal position I read `0x64 0x00 0x00`: clearly, the gas pedal position is within the first byte of the message and I might be tempted to define the signal `GAS_POS` as:
+- Signal size: always use the smallest amount of bits possible. For example, let's say I'm reverse engineering the gas pedal position and I've determined that it's in a 3 bytes message. For 0% pedal position I read a message value of `0x00 0x00 0x00`, while for 100% of pedal position I read `0x64 0x00 0x00`: clearly, the gas pedal position is within the first byte of the message and I might be tempted to define the signal `GAS_POS` as:
     ```
     SG_ GAS_POS : 7|8@0+ (1,0) [0|100] "%" PCM
     ```
diff --git a/requirements.txt b/requirements.txt
new file mode 100644
index 00000000000000..c1ac27ec9243cb
--- /dev/null
+++ b/requirements.txt
@@ -0,0 +1,7 @@
+Cython==0.29.14
+flake8==3.7.9
+Jinja2==2.10.3
+pycapnp==0.6.4
+pylint==2.4.3
+pyyaml==5.1.2
+scons==3.1.1