Attention: This is an updated copy of post 107 gleaned from the ISLE project’s document. ONLY the headings from the original document and the annotations which are specific to Digital.Grinnell appear in this document!

Note: This update procedure was NOT performed “locally”, as recommended, due to substantial errors encountered in my last attempt to update. Rather than diving down that rabbit hole, again, I elected to attempt this update on our staging server, DGDockerX on 2021-Sep-27.

Update ISLE to the Latest Release

Important Information

# stop the docker service
$ sudo service docker stop

# download the latest docker binary and replace the current outdated docker
# DEPRECATED WAY TO UPGRADE DOCKER: $ sudo wget -O /usr/bin/docker
$ sudo yum update docker-engine

# start the docker service
$ sudo service docker start

# check the version
$ sudo docker version

# check the images and containers
$ sudo docker images
$ sudo docker ps
$ sudo docker ps -a

Update Local (personal computer)

As mentioned above, this work is being conducted in staging rather than local, on DGDockerX in the /home/islandora/ISLE directory and the dg-isle and dg-islandora directories there.

My new branch is named isle-update-v1.5.11.

Output from git pull follows.

╭─islandora@dgdockerx ~/ISLE/dg-isle ‹isle-update-v1.5.11›
╰─$ git pull icg-upstream main
 * branch            main       -> FETCH_HEAD
Auto-merging docs/install/
Auto-merging docker-compose.staging.yml
Auto-merging docker-compose.production.yml
Auto-merging docker-compose.local.yml
Merge made by the 'recursive' strategy.
 docker-compose.demo.yml                    | 14 +++++++-------
 docker-compose.local.yml                   | 16 ++++++++--------
 docker-compose.production.yml              | 16 ++++++++--------
 docker-compose.staging.yml                 | 14 +++++++-------
 docker-compose.test.yml                    | 16 ++++++++--------
 docs/cookbook-recipes/  |  6 +++---
 docs/install/ | 22 +++++++++++++++++++++-
 docs/install/        | 45 +++++++++++++++++++++++++++++++++++++++++++++
 docs/release-notes/       | 64 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 docs/release-notes/       | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 docs/release-notes/        | 70 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 docs/release-notes/        | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 mkdocs.yml                                 |  7 ++++++-
 13 files changed, 377 insertions(+), 43 deletions(-)
 create mode 100644 docs/install/
 create mode 100644 docs/release-notes/
 create mode 100644 docs/release-notes/
 create mode 100644 docs/release-notes/
 create mode 100644 docs/release-notes/

There were NO merge conflicts so ratom (see Remote Atom) was not needed.

There really should be an additional step here since you must edit, or at least check your .env file! I changed mine to read as follows:


With an active VPN connection, I am happy to report that the staging site is now working at

Preliminary tests look good, and a search for “Ley” returns a very short list of objects that do exist in my DG-STAGING test repository.

I wasn’t able to execute the sequence as presented above. Instead, I did this:

╭─islandora@dgdockerx ~/ISLE/dg-isle
╰─$ git add .
╭─islandora@dgdockerx ~/ISLE/dg-isle
╰─$ git commit -m "Updated and working on DGDockerX"
╭─islandora@dgdockerx ~/ISLE/dg-isle
╰─$ git push origin isle-update-v1.5.11

Hold on, there’s one more significant part of the update process that’s not covered here, updating the Drupal and Islandora code that is not technically part of ISLE, but probably should be?

My process for updating that went something like this:

╭─islandora@dgdockerx ~
╰─$ cd ~/ISLE/dg-islandora
╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹main›
╰─$ git pull
╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹main›
╰─$ git checkout -b update-sept-27
╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹update-sept-27*›
╰─$ docker exec -it isle-apache-dgs bash
root@e97835142685:/# cd /var/www/html/sites/default/
root@e97835142685:/var/www/html/sites/default# rm -fr files/webform/*
root@e97835142685:/var/www/html/sites/default# drush up

The drush up command was invoked to pull in all of the latest updates to Drupal v7, and there were many, including an update to Drupal’s core, now at v7.82. Since the core got updated, I had to eventually revert changes to /var/www/html/.htaccess since those updates typically remove a line that ISLE requires to function properly. I confirmed that the changes made by drush up did indeed make their way into ~/ISLE/dg-islandora by checking git status. I managed to revert the changes to .htaccess using sudo git checkout -- .htaccess.

After making those changes I found it necessary to restart the stack using:

╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹update-sept-27*›
╰─$ cd ~/DG-STAGING
╭─islandora@dgdockerx ~/DG-STAGING ‹main*›
╰─$ ./

This time I did NOT have to run several of the ./Update-*.sh scripts in ~/DG-STAGING in order to get everything working properly. So, I pushed my dg-islandora changes to Github using:

╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹update-sept-27*›
╰─$ git add --all .
╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹update-sept-27*›
╰─$ git commit -m "Updates from DGDockerX"
[update-sept-27 e27a34c] Updates from DGDockerX
 183 files changed, 954 insertions(+), 666 deletions(-)
 mode change 100644 => 100755 scripts/
 mode change 100644 => 100755 scripts/
 mode change 100644 => 100755 scripts/
 rewrite sites/all/modules/contrib/views/README.txt (70%)
 ╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹update-sept-27›
 ╰─$ git pull origin main
 Username for '': Digital-Grinnell
 Password for '': xxxxxxxxxxxxxxx
  * branch            main       -> FETCH_HEAD
 Already up-to-date.

At this point I did another cd ~/DG-STAGING; ./ just to ensure things still work properly. Another ./ was also needed.


╭─islandora@dgdockerx ~/DG-STAGING ‹main›
╰─$ cd ~/ISLE/dg-islandora
╭─islandora@dgdockerx ~/ISLE/dg-islandora ‹update-sept-27›
╰─$ git push origin update-sept-27
Username for '': Digital-Grinnell
Password for '': xxxxxxxxxxxxxxx
Counting objects: 558, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (288/288), done.
Writing objects: 100% (292/292), 35.30 KiB | 0 bytes/s, done.
Total 292 (delta 253), reused 0 (delta 0)
remote: Resolving deltas: 100% (253/253), completed with 227 local objects.
remote: Create a pull request for 'update-sept-27' on GitHub by visiting:
 * [new branch]      update-sept-27 -> update-sept-27

Update Staging Server

Ok, at this point I’ve already got our staging server up-to-date, including the addition of my purge-tmp-files script successfully added to the Apache container’s /etc/cron.hourly directory, but the ownership on that script is islandora:islandora and it needs to be root:root. So, I need to change that from inside the isle-apache-dgs container like so: root@bc83fc8bb3c3:/etc/cron.hourly# chown root:root purge-tmp-files.

My next steps will be to backup the production database and /var/www/html/sites/default/files, merge all of the dg-isle and dg-islandora repository changes into their respective main branches, and repeat all of my implementation and testing in staging again. For production backup look at ~/ISLE/DEPLOY/ on DGDocker1 for guidance!

I used the ~/ISLE/DG-STAGING/ and ~/ISLE/DG-STAGING/ scripts on DGDockerX to restart the stack after capturing the production database and /var/www/html/sites/default/files contents. It worked nicely except for a warning about permissions on public://backup_migrate/manual. I reran the ~/ISLE/DG-STAGING/ script and the warning went away.

I subsequently performed a git add .; git commit -m "message"; git push origin update-sept-27 command sequence from both the ~/ISLE/dg-islandora and a similar sequence, but with branch isle-update-v1.5.11 in ~/ISLE/dg-isle repositories to commit all changes. I subsequently opened pull requests to merge both back to the corresponding main branches of their respective repositories.

Next update will be to our production server, DGDocker1, where I hope to repeat this process to-the-letter.

Working Here !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Add a note about making sure we hold on to, and use, the old acme.json file that’s in ~/ISLE/dg-isle/config/proxy/!

Update Production Server

When you are confident that your Staging installation is working as expected:

  • Repeat the same above “Update Staging Server” process but do so on your Production server environment.

Additional Resources

Please post questions to the public Islandora ISLE Google group, or subscribe to receive emails.

One hiccup in the production update… I encountered this error when trying to initiate an IMI import:

RuntimeException: Unable to create the cache directory (/var/www/private/ed). in Twig\Cache\FilesystemCache->write() (line 57 of /var/www/html/sites/all/modules/islandora/islandora_multi_importer/vendor/twig/twig/src/Cache/FilesystemCache.php).

The problem appeared to be ownership of the /var/www/public directory in the Apache container. The public folder was owned by islandora:islandora so I opened a shell into Apache and did cd /var/www/; chown -R islandora:www-data public. That seems to have fixed the problem nicely.

End of: Update ISLE to the Latest Release

And that’s a wrap. Until next time…