Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
getting-started:updating [2018/05/02 20:35]
83.162.167.127 [Updating the BrewPi Spark firmware with DFU]
getting-started:updating [2018/05/02 22:32] (current)
Elco Jacobs [Updating the BrewPi Spark firmware with DFU]
Line 164: Line 164:
 <​code>​ <​code>​
 docker pull brewpi/​brewpi-raspbian docker pull brewpi/​brewpi-raspbian
-docker run --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-raspbian python utils/​flashDfu.py --trigger +docker run -it --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-raspbian python utils/​flashDfu.py --trigger 
-docker run --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-raspbian python utils/​flashDfu.py --noreset+docker run -it --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-raspbian python utils/​flashDfu.py --noreset
 </​code>​ </​code>​
  
Line 205: Line 205:
 Finally, we can start a docker container for single use that is destroyed afterwards (''​--rm''​) and run the flashDfu.py script directly inside the container. Finally, we can start a docker container for single use that is destroyed afterwards (''​--rm''​) and run the flashDfu.py script directly inside the container.
 <​code>​ <​code>​
-docker run --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --trigger +docker run -it --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --trigger 
-docker run --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --noreset+docker run -it --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --noreset
 </​code>​ </​code>​
  
Line 219: Line 219:
 We can start a docker container for single use that is destroyed afterwards (''​--rm''​) and run the flashDfu.py script directly inside the container: We can start a docker container for single use that is destroyed afterwards (''​--rm''​) and run the flashDfu.py script directly inside the container:
 <​code>​ <​code>​
-docker run --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --trigger +docker run -it --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --trigger 
-docker run --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --noreset+docker run -it --name brewpi-dfu --privileged -v ~/​brewpi-data:/​data --rm brewpi/​brewpi-ubuntu python utils/​flashDfu.py --noreset
 </​code>​ </​code>​