cool, the last run confirmed that our ubuntu host can run AppImages and fuse is not an issue

 * https://github.com/maltfield/cross-platform-python-gui/runs/725641922?check_suite_focus=true

Let's see if I can figure out how to tell it to use the docker image for a single step only *after* we run a command on the docker host (ubuntu) to setup fuse. Oh, we'll also want to checkout the code before the script runs -- both actions inside the docker container. Possible?

If this is too hard, I'll try harcoding the git clone in my script.

Worst case, I'll abandon docker and just do everything directly in ubuntu.

Author: maltfield

.github/workflows/build.yml

@@ -12,28 +12,27 @@ jobs:
   linux:
     runs-on: ubuntu-latest
 #    container: debian:buster-slim
-#
+
     steps:
-    - uses: actions/checkout@v2
-    - name: Execute script to build linux AppImage
+    - name: First setup fuse on the docker host
       run: |
         sudo apt-get install fuse
         sudo lsmod
         sudo modprobe fuse
         sudo lsmod
-        wget -O /tmp/python3.7.AppImage https://github.com/niess/python-appimage/releases/download/python3.7/python3.7.7-cp37-cp37m-manylinux2014_x86_64.AppImage
-        chmod +x /tmp/python3.7.AppImage
-        /tmp/python3.7.AppImage -c 'print("hello")'
       shell: bash
-#
-#    - name: Execute script to build linux AppImage
-#      run: "build/linux/buildAppImage.sh"
-#      shell: bash
-#
-#    - uses: actions/upload-artifact@v2
-#      with:
-#        name: Linux AppImage (x86_64)
-#        path: dist/
+
+    - name: Execute script to build linux AppImage
+      uses:
+      - actions/checkout@v2
+      - docker://debian:buster-slim
+      run: "build/linux/buildAppImage.sh"
+      shell: bash
+
+    - uses: actions/upload-artifact@v2
+      with:
+        name: Linux AppImage (x86_64)
+        path: dist/
 
   windows:
     runs-on: windows-latest