Update php container Dockerfile to point at specific version of composer

[jaltekruse]

• add a new npm script to run all tests besides the DoenetML ones
• electron runs about 25% faster for me, so I set that as the browser for this new script, to have a quick signal if the app side is likely in a good state. There is a tiny chance chrome behaves differently, but they are both based on Chromium

I ran into an issue after cleaning out my containers completely, I had messed things up while trying to backport the LTI stuff to 5.4, after starting out from a clean environment I was getting this failure on requests to the php server. Pinning to this version of composer and rebuilding my container with npm run buildx:php fixed it for me. @Lyanthropos do you think pinning a version like this makes sense?

Apparently docker does not very proactively pull in new versions of containers that you depend on if it has any version cached locally. Which I guess is the reason I ran into this but everyone else has been fine. Although I am curious about Duane recently setting up his laptop and not hitting this.

https://stackoverflow.com/questions/74141587/does-docker-from-keyword-in-dockerfile-look-for-the-newest-image

I have a CI Runner that automatically builds a docker image from a Dockerfile. My docker image is based on another docker image. So the beginning of my Dockerfile looks like this:

FROM linktoimage/imagename:latest
Does docker check during the build process if my local version of imagename is still the latest (similar to docker pull? Because i noticed that my ci runner shows sn older version of imagename if i run docker images on it

Stackoverflow Answer
No, docker will not do this by default because of the build cache. It will use whatever existing image it has locally in the cache [1].

You can however enable the behavior you desire by using the --no-cache option:
$ docker build . --no-cache=true

                 Status: 500 - Internal Server Error
                 Headers: {
                   "date": "Tue, 15 Nov 2022 20:07:16 GMT",
                   "server": "Apache/2.4.48 (Unix)",
                   "x-powered-by": "PHP/5.4.45",
                   "access-control-allow-origin": "*",
                   "access-control-allow-headers": "access",
                   "access-control-allow-methods": "POST",
                   "access-control-allow-credentials": "true",
                   "content-type": "application/json",
                   "connection": "keep-alive",
                   "keep-alive": "timeout=5",
                   "transfer-encoding": "chunked"
                 }
                 Body: <br />
                 <b>Fatal error</b>:  Composer 2.3.0 dropped support for autoloading on PHP <5.6 and you are running 5.4.45, please upgrade PHP or use Composer 2.2 LTS via    "composer self-update --2.2". Aborting.
                  in <b>/usr/local/apache2/htdocs/api/vendor/autoload.php</b> on line <b>20</b><br />

[jaltekruse]

This isn't ready for immediate merging, I want to get input from others, primarily Emilio first.

[dqnykamp]

This isn't ready for immediate merging, I want to get input from others, primarily Emilio first.

Convert to draft PR?

[jaltekruse]

apparently this doesn't work, still trying to see if there is a way to do an exclude list rather than an include list with a directory

[dqnykamp]

We could always change the structure so that the DoenetML specs are in one directory and the rest are in another directory so that you can use a simple --spec with one directory.

Eventually, the plan is to move DoenetML into the DoenetML repository, at which point the specs will be separate anyway.