Archipelago-deployment-live: upgrading Archipelago 1.5.0 to 1.6.0 (Drupal 10.4.x to 10.5.x)
What is this documentation for?
If you already have a well-set-up and well-loved Archipelago (1.5.0) running Drupal 10.4 or more recent (D10), this documentation will allow you to update to 1.6.0 on latest Drupal 10.5.x without any major issues. For Archipelago 2.0.0 under Drupal 11, please read first the complete deployment https://github.com/esmero/archipelago-deployment-live/blob/2.0archipelago-deployment-live-readme.md and then follow the corresponding upgrade guide to D11 at https://github.com/esmero/archipelago-deployment-live/blob/2.0.0/archipelago-deployment-UpgradeFromD10toD11.md.
This documentation is meant to be a guide/helper, not a single-click-magic solution. Why? Because your Drupal environment and your local github branches for this whole project might have diverged really lot from a vanilla Archipelago base deployment. You might have new templates, custom composer.json, new modules, changed webforms and Views. That is not an Archipelago issue, more like a 'How do I keep any Drupal instance, YAML files, custom configurations and modules in version control and in sync as I upgrade other parts' issue.
Requirements
- An archipelago-deployment-live instance 1.5.0 (working, tested) deployed using provided instructions via Docker and running Drupal 10.
- Attention span/focus to read/follow each instruction (even if they feel redundant and maybe even a drag). Don't do an update if you are tired/in a rush. Avoid Upgrades on a Friday. Ok?
- Basic knowledge, patience and instincts (+ courage) on how to run Terminal Commands,
composeranddrush. - Patience(again). You can't skip steps here.
- For shell Commands documented here please copy line by line--not the whole block.
- You are running already version control and know how to git pull/push/merge.
- Your current git tree (the branch you are running) has no uncommitted/untracked changes. This is important. Make sure your
git statusandgit logare clean.
Backing up and preparing for the upgrade
Backups are always going to be your best friends. Archipelago's code, database, and settings are mostly self-contained in your current archipelago-deployment-live repo folder, and backing up is simple because of that.
Step 1:
Export/backup all of your live Archipelago 1.5.0, Drupal 10 configurations (this allows you to compare/come back in case you lose something custom during the upgrade).
docker exec esmero-php mkdir config/backup
docker exec esmero-php drush cex --destination=/var/www/html/config/backup
Step 2:
On a terminal, cd into your running archipelago-deployment-live folder, then cd inside the deploy/ec2-docker subfolders and shut down your docker-compose ensemble by running the following:
docker-compose down
Step 3:
Verify that all containers are actually down. The following command should return an empty listing:
docker ps
If anything is still running, wait a little longer and run the command again.
Step 4:
Now let's tar.gz the whole ensemble with data and configs. We will exclude here the local source caches generated by Cantaloupe and also the minio data folder. If these or not exist will depend on how custom your
deployment is setup.
As an example we will save the gzipped tar into your $HOME folder. As a good practice we append the current date (YEAR-MONTH-DAY) to the filename. Here we assume today is December 15th of 2025.
Please make sure you have enough space for this operation. If not use a different partition/mount. Databases and Solr might use a lot of space. As noted before, we are, on purpose, ignoring archipelago-deployment-live/data_storage/minio-data (in case you are not running S3 on the cloud) but you could include it if you have plenty of space left on your backup destination path/mount/drive.
We will cd back to the parent folder of your running archipelago-deployment-live folder (and we assume archipelago-deployment-live is how you named your git cloned folder), so three levels down, assuming you are right now inside archipelago-deployment-live/deploy/ec2-docker
cd ../../..
sudo tar --exclude=archipelago-deployment-live/data_storage/iiifcache --exclude=archipelago-deployment-live/data_storage/minio-data --exclude=archipelago-deployment-live/data_storage/iiiftmp -czvpf $HOME/archipelago-deployment-D10-20251215.tar.gz archipelago-deployment-live
The process may take a few minutes. Now let's verify that all is there and that the tar.gz is not corrupt.
tar -tvvf $HOME/archipelago-deployment-D10-20251215.tar.gz
You will see a listing of files, and at the end you will see something like this: Archive Format: POSIX pax interchange format, Compression: gzip. If corrupt (Do you have enough space? Did your ssh connection drop?) you will see the following:
tar: Unrecognized archive format
If something went wrong, fix your command, make sure you have plenty of space (delete the wrong tar.gz too!) and try again. Don't move to a next step UNTIL your backup is safe and verified.
Step 5:
cd again into your running archipelago-deployment-live folder, then cd inside the deploy/ec2-docker
Restart your docker-compose ensemble, and wait a little while for all to start.
docker-compose up -d
Step 6 (Optional):
Sometimes it is easier to clone Archipelago Deployment Live 1.6.0 into another folder (outside of the root of your running one) in your system (an undeployed version/never to be deployed). That way you can copy selectively files, diff folders/compare shipped configs with this vanilla release and your running instance.
Good. Now it's safe to begin the Software upgrade process. This guide is separated into two upgrade process. First code base (Archipelago/Drupal). Once that is done and tested and you are all good and happy, you can optionally (but ideally) move into Services/Docker Container and services upgrades, which for this release are only suggested and are less chalenging that previos ones.
Upgrading to Archipelago 1.6.0 (Software/Code)
Step 0: Get familiar with what changed.
We mean this. This is a new step. Running a Production Server requires some informed decision making and thus, we believe, a good pre-step is reviewing what changed between releases.
In 1.5.0 we introduced the jq command to (attempt) to teach you all how to approach a composer.json level upgrade. That is still valid. But also, to simplify the process this time, our new composer.json (compared to the previous release one) was shipped using the same order of appearance of dependencies, which means a simple git diff would give you pretty much the same experience. So let's do that here. Inside your Archipelago deployment live git root (folder) run
git fetch
git diff -R origin/1.6.0 -- drupal/composer.default.json
diff --git b/composer.json a/composer.json
index 818d6e3..4558d1e 100644
--- b/composer.json
+++ a/composer.json
@@ -22,7 +22,7 @@
"require": {
"php": ">=8.1",
"mglaman/composer-drupal-lenient": "^1",
- "archipelago/ami": "0.9.0.x-dev",
+ "archipelago/ami": "1.0.0.x-dev",
"archipelago/archipelago_subtheme": "1.5.0.x-dev",
"aws/aws-php-sns-message-validator": "^1.5",
"aws/aws-sdk-php": "^3.63",
@@ -34,24 +34,24 @@
"drupal/bamboo_twig": "5.x-dev",
"drupal/bootstrap_barrio": "^5.5",
"drupal/calendar": "^1.0@alpha",
- "drupal/redis": "^1.7",
+ "drupal/redis": "^1",
"drupal/config_inspector": "dev-2.1.x",
"drupal/config_update": "2.0.x-dev",
"drupal/context": "^5.0@RC",
- "drupal/core": "^10.4",
- "drupal/core-composer-scaffold": "^10.4",
- "drupal/core-project-message": "^10.4",
- "drupal/core-recommended": "^10.4",
- "drupal/devel": "^5.1",
+ "drupal/core": "^10.5",
+ "drupal/core-composer-scaffold": "^10.5",
+ "drupal/core-project-message": "^10.5",
+ "drupal/core-recommended": "^10.5",
+ "drupal/devel": "^5.5",
"drupal/display_field_copy": "^2.0",
"drupal/ds": "^3.23",
"drupal/facets": "2.0.x-dev",
"drupal/field_permissions": "^1.0@RC",
- "drupal/file_mdm": "^2",
+ "drupal/file_mdm": "^3.0",
"drupal/file_mdm_exif": "^2",
"drupal/flag": "^4.0",
"drupal/google_api_client": "^4",
- "drupal/imagemagick": "^3",
+ "drupal/imagemagick": "^4.0",
"drupal/imce": "^3.0",
"drupal/inline_entity_form": "1.x-dev",
"drupal/jquery_ui_datepicker": "^2.0",
@@ -67,7 +67,7 @@
"drupal/schema_metatag": "^1.3",
"drupal/search_api": "1.x-dev@dev",
"drupal/search_api_attachments": "^9.0",
- "drupal/search_api_autocomplete": "^1.2",
+ "drupal/search_api_autocomplete": "^1.0",
"drupal/search_api_solr": "^4.3",
"drupal/smtp": "^1.0",
"drupal/tokenuuid": "^2.0",
@@ -92,22 +92,22 @@
"react/event-loop": "^1.5",
"react/promise": "^3.2",
"solarium/solarium": "^6",
- "strawberryfield/format_strawberryfield": "1.5.0.x-dev",
- "strawberryfield/strawberry_runners": "0.9.0.x-dev",
- "strawberryfield/strawberryfield": "1.5.0.x-dev",
- "strawberryfield/webform_strawberryfield": "1.5.0.x-dev",
+ "strawberryfield/format_strawberryfield": "1.6.0.x-dev",
+ "strawberryfield/strawberry_runners": "1.0.0.x-dev",
+ "strawberryfield/strawberryfield": "1.6.0.x-dev",
+ "strawberryfield/webform_strawberryfield": "1.6.0.x-dev",
"swaggest/json-schema": "^0.12.10",
"vlucas/phpdotenv": "^5.6",
"webflo/drupal-finder": "^1.0.0",
"wikibase/data-model": "9.6.1",
"drupal/facets_date_range": "^1.0@beta",
- "drupal/better_exposed_filters": "^7",
+ "drupal/better_exposed_filters": "^7.1",
"monolog/monolog": "^2.9",
"egulias/email-validator": "^4",
"drupal/upgrade_status": "^4.3",
"drupal/jquery_ui_effects": "^2.0",
"drupal/jquery_ui": "^1.6",
- "archipelago/fragaria": "0.2.0.x-dev",
+ "archipelago/fragaria": "0.4.0.x-dev",
"drupal/color": "1.x-dev@dev",
"drupal/seven": "^1.0",
"drupal/hal": "^2.0",
@@ -117,7 +117,7 @@
"drupal/stable": "^2.0",
"drupal/form_mode_manager": "2.x-dev@dev",
"drupal/rest_oai_pmh": "2.0.x-dev",
- "cebe/php-openapi": "1.8",
+ "cebe/php-openapi": "^1.8",
"league/openapi-psr7-validator": "0.22",
"drupal/views_load_more": "^2.0@RC",
"drupal/codemirror_editor": "^2.0",
@@ -125,10 +125,11 @@
"archipelago/archipelago_subtheme_chiloe": "dev-main"
},
"require-dev": {
- "drupal/core-dev": "^10.4",
+ "drupal/core-dev": "^10.5",
"mglaman/drupal-check": "^1.1",
"phpcompatibility/php-compatibility": "dev-develop",
- "rector/rector": "^0.14.0"
+ "rector/rector": "^1",
+ "phpstan/phpstan": "^1"
},
"conflict": {
"drupal/drupal": "*"
See? Changes without your customizations are not too many. Red means removed, green added. Most of the time it will be a matching (version bump) removal/addition of a package, which for our purpouses here will become a
docker exec -ti esmero-php bash -c "composer require package/in-green:version-in-green --no-update" command.
Now, to compare your live and active composer.json (which is not tracked) against 1.6.0, please run:
git diff origin/1.6.0:drupal/composer.default.json drupal/composer.json
Note: Bear in mind that because you are comparing two different file names, and your local one might be untracked, you can't git diff using -R (reversed one), so new additions to 1.6.0 will show up (in red) as removals instead.
If you see green only (remember, your active composer.json against the new remote composer.default.jsonare not reversed), most likely it would be ONE of your custom added modules which compare to ours does not exist (thus in GREEN only). We won't touch those, because we don't ship archipelago with every module you might have added. It would be up to you to decide (or act on when you run the final command of step 1) if you want/need/can update those.
Note 2: Important to know/learn. Even if all packages are managed by composer, blindly uninstalling (not upgrading...we mean actually removing) any package that starts with drupal/ without first drush pm-uninstall it from Drupal will lead to errors and constant notifications from there on that you have an installed module that has missing source files. Don't do it! Always cleanly uninstall components/modules first from Drupal via drush or the UI if you are removing them. Then, once that is done, composer delete them. You have been warned! (twice) (:
Step 1. Updates for key Drupal and Archipelago modules
Now that you know (if you read all we tried to explain in step 0) how commands for an updated are generated, you can actually start upgrading.
Start the actual upgrade process by running the following commands (line by line):
docker exec -ti esmero-php bash -c "composer require archipelago/ami:1.0.0.x-dev strawberryfield/strawberry_runners:1.0.0.x-dev archipelago/archipelago_subtheme:1.6.0.x-dev strawberryfield/strawberryfield:1.6.0.x-dev strawberryfield/webform_strawberryfield:1.6.0.x-dev strawberryfield/format_strawberryfield:1.6.0.x-dev archipelago/fragaria:0.4.0.x-dev archipelago/archipelago_subtheme_chiloe:dev-main --update-with-dependencies --no-update"
Now Drupal Core and friends
docker exec -ti esmero-php bash -c "composer require drupal/core:^10.5 drupal/devel:^5.5 drupal/core-composer-scaffold:^10.5 drupal/core-project-message:^10.5 drupal/core-recommended:^10.5 --update-with-dependencies --no-update"
And the dev dependencies
docker exec -ti esmero-php bash -c "composer require drupal/core-dev:^10.5 rector/rector:^1 phpstan/phpstan:^1 --dev --update-with-dependencies --no-update"
And some contributed modules we normally ship with.
docker exec -ti esmero-php bash -c "composer require drupal/redis:^1 drupal/file_mdm:^3.0 drupal/imagemagick:^4.0 drupal/search_api_autocomplete:^1.0 drupal/better_exposed_filters:^7.1 cebe/php-openapi:^1.8 --update-with-dependencies --no-update"
From inside your archipelago-deployment-live repo folder we are now going to open up file permissions for some of your most protected Drupal files.
sudo chmod 777 drupal/web/sites/default
sudo chmod 666 drupal/web/sites/default/*settings.php
sudo chmod 666 drupal/web/sites/default/*services.yml
Step 2. Applying Composer updates/changes.
And now we will make all have an actual effect!
docker exec -ti esmero-php bash -c "composer update -W"
Well done! If you see no issues and all ends in Green colored messages, all is good!
What if all is not OK, and I see red and a lot of dependency explanations?
Just in case try to run this agai.
docker exec -ti esmero-php bash -c "composer update -W"
Sometimes the internet is a pokey place and remote servers timeout, things are strange. Sometimes people skip steps (did you?). If after trying again and also self-doubting and retracing your steps, things are still strange, you might need to do some troubleshooting.
Maybe you have custom modules that are NO longer Drupal 10.5 compatible? If so, you may see errors. You should check each package website's (normally https://www.drupal.org/project/the_module_name) to see if there is a more recent Drupal 10 compatible version.
If so run:
docker exec -ti esmero-php bash -c "composer require 'drupal/the_module_name:^VERSION_NUMBER_THAT_WORKS_ON_DRUPAL10_5' --update-with-dependencies --no-update"
followed by
docker exec -ti esmero-php bash -c "composer update -W"
Repeat until no more errors pop-up.
If a Drupal 10 compatible version of a module is not available, try to find a replacement module that does something similar, but in any case you may end up having to remove it before proceeding. Give us a pin on our public slack channel/google group/open a github ISSUE if you find yourself uncertain about this.
docker exec -ti esmero-php bash -c "drush pm-uninstall the_module_name"
docker exec -ti esmero-php bash -c "composer remove drupal/the_module_name --no-update"
docker exec -ti esmero-php bash -c "composer update -W"
If you keep seeing error messages of missing dependencies, invalid (stuck/old versions) libraries or conflicts, review each message and check what modules/libraries are not allowing you to upgrade. One way of understanding the chained dependency errors is to run:
docker exec -ti esmero-php bash -c "composer why some_namespace/some_library"
Example given:
docker exec -ti esmero-php bash -c "composer why solarium/solarium"
Will output:
drupal-composer/drupal-project 1.6.0.x-dev requires solarium/solarium (^6)
drupal/search_api_solr 4.3.10 requires solarium/solarium (^6.3.7)
If a given library/module/dependency is only required by drupal-composer/drupal-project you have space to loosen it up to a higher/more permissive version. If it dependends on other library/modules, those might be the culprits of not being able to upgrade it and normally the solution is to upgrade that library first (always using the --no-update argument) and then run docker exec -ti esmero-php bash -c "composer update -W" again.
Step 4: Update your Database (and run hook updates)
Now run one final database update command:
docker exec -ti esmero-php bash -c "drush updatedb"
Step 5: Optional Syncs (Optional)
This is optional ,but very recommended. To be sure you are getting what you want/need and will not end overriding things you carefully modified already, we encourage you to run a local Archipelago 1.6.0, explore the UI, ingest, do some searches and the experience the new settings first hand and new metadata displays. It takes 5-10 minutes of your live and will provide an excellent visual insight of what is new. For that go to https://github.com/esmero/archipelago-deployment and follow the guide matching your local OS. You won't regret it.
After playing with a new 1.6.0 safely in your local, you can decide if syncing your new Archipelago 1.6.0 is needed and bring in chosen latest configs and settings. This requires you do fetch, either via git or manually via wget or curl newer configs from https://github.com/esmero/archipelago-deployment-live/tree/1.6.0/drupal/config/sync into the same folder structure/location of your deployment or use the local cloned copy you made at Step 6 of Backing up and preparing for the upgrade.
For this you have three options (no worries, actually do worry, just remember you made a backup! Did you? Double check!):
Option 1. A Partial Sync, which will bring new configs and update existing ones but will not remove ones that only exist in your custom setup, e.g. new Webforms or View Modes.
docker exec esmero-php drush cim --partial
You will get a list. You can always have second thoughs and baul out here if you feel unsure. Select "YES" if you decide to proceed.
Option 2. A Complete Sync, which will bring new things and update existing but will also remove all the ones that are not part of 1.5.0. It's a like clean (danger!) factory reset.
docker exec esmero-php drush cim
You will get a list. You can always have second thoughs and baul out here if you feel unsure. Select "YES" if you decide to proceed.
Option 3. A Selective Partial Sync, which will bring manually picked configs and update existing ones. Won't remove new ones you added. Won't bring all changed 1.6.0
To do so, create inside drupal/config a new folder named "sync_handpicked". Fetch or copy any (or or more) YAML files from the 1.6.0 release (from github or your locally cloned copy) you want to sync. E.g. Just the search index, https://github.com/esmero/archipelago-deployment-live/blob/1.6.0/drupal/config/sync/search_api.index.default_solr_index.yml into that folder. Y
docker exec esmero-php drush cim --source config/sync_handpicked
You might see some warnings related to modules dealing with previously non-existent data—-no worries, just ignore those. One notable is a Search API/ and autocomplete warning. We are running a @dev version and Drupal's dependencies (e.g 8.x-1.2.0) can't handle @dev.
Step 6: Update (or not - Optional) your Metadata Display Entities and menu items
Recommended: If you want to add new templates and menu items 1.6.0 provides, you need to fetch everything from this remote https://github.com/esmero/archipelago-deployment-live/tree/1.6.0/drupal/d8content or copy from your locally cloned 1.6.0, to your local installation into the same folder structure/location,
then replace your local deploy.sh and update_deployed.sh scripts which can be found inside your base archipelago deployment folder inside drupal/scripts/archipelago with
https://raw.githubusercontent.com/esmero/archipelago-deployment-live/refs/heads/1.5.0/drupal/scripts/archipelago/deploy.sh
and
https://raw.githubusercontent.com/esmero/archipelago-deployment-live/refs/heads/1.6.0/drupal/scripts/archipelago/update_deployed.sh
from the new release and, as described in the general (from zero) 1.6.0 Deployment Instructions replace the http://esmero-web with your real domain.
On a terminal navigate to your base archipelago deployment folder and run the following command replacing your.domain.org with your actual domain.
sed -i 's/http:\/\/esmero-web/https:\/\/your.domain.org/g' drupal/scripts/archipelago/deploy.sh
sed -i 's/http:\/\/esmero-web/https:\/\/your.domain.org/g' drupal/scripts/archipelago/update_deployed.sh
and then run:
docker exec -ti esmero-php bash -c 'scripts/archipelago/deploy.sh'
This command will only add templates you don't have and fail (good) one same UUID/exiting ones.
Important: If you don't download/sync/git/merge or copy from your local cloned 1.6.0 (or your prefered method) then the command will add nothing, since you will be running this command against 1.5.0 content.
Once that is done, you could (danger!) * choose to update all Metadata Displays (twig templates) we ship with new 1.6.0 versions (including a new IIIF manifest that fetches CWS Children from multiple levels from Solr Stored RAW JSON, DataCite Schema V4, improved OAI templates, AMI set Description template, etc). Before you do this, we strongly recommend that you first make sure to manually (copy/paste or download via the UI - new in Archipelago 1.6.0!) backup any Twig templates you have modified. If unsure, do not run* the command that comes after this warning! You can always manually copy the new templates from the d8content/metadatadisplays folder which contains text versions (again, copy/paste) of each shipped template you can pick and use when you feel ready.
If you are sure (like really?) you really want to overwrite the ones you modified (sure, just checking?), then you can run this (make sure you edit that file):
docker exec -ti esmero-php bash -c 'scripts/archipelago/update_deployed.sh'
Done! (For realz now)
Step 7
Please login to your Archipelago and test/check all is working! Enjoy Archipelago 1.6.0 under Drupal 10. Thanks! Also please keep all your new changes under version control. Check what has changed. git add and git commit -m "What i changed" as needed.
Upgrading to Archipelago 1.6.0 new Services and Containers
Step 1: Edit docker-compose.yml
For this release there no larger updates on the Docker backend level but we do include a few useful production example of health monitoring for Cantaloupe and Log Size Limits. Solr 9 was updated from 9.8 to 9.10 and Database (MYSQL and MariaDB) also got a version bumps. As with 1.5.0 Esmero NLP with Machine Learning Model Endpoints is not meant for public/anonymous access. Reasons are many (same as before): some technical (CPU/GPU and memory consumption not suited for a medium server) but mostly about usefulness, use cases, real needs driving the use of the tools we developed and the very much needed Community Discussion and Consensus on our Field's (GLAM) ethical concerns about this. That said 1.6.0 includes larger code updates on ML Search API integration and UI/UX interactions, so you are free to decide if those tools are for you. drupal/config/sync_ml holds Views/Post processor YAML configs if you feel so.
If you decide to upgrade your services please review one of these (based on your running Platform): - https://github.com/esmero/archipelago-deployment-live/blob/1.6.0/deploy/ec2-docker/docker-compose-aws-s3-arm64.yml - https://github.com/esmero/archipelago-deployment-live/blob/1.6.0/deploy/ec2-docker/docker-compose-aws-s3.yml
And selectively copy images/enviromentals into your production docker-compose.yml file. Please also read and use General Installation guide for 1.6.0 to ensure you are using the right, and new, .env enviromentals. Basically have it at hand to validate all your changes.
Special NOTE: Solr 9.10, same as 9.8, uses Modules instead of libraries and also uses a different Solr OCR Highlight version, which can be seen here. The old one from 1.5.0 still works but you are encouraged to remove the library solr-ocrhighlighting-0.9.4.jar and replace with 1.6.0's shipped solr-ocrhighlighting-0.9.5.jar. A Simple esmero-solr restart is enough after that.
Special Note2: Anubis. Same as in 1.5.0. Anubis is a Web Application Firewall that will aid in traffic control generated by AI/ML Bots. It uses a special NGINX configuration and special .env variables. If you are not yet running anubis, don't move it right now. You can check the General Installation guide for 1.6.0 to install it, since you are actually NOT upgrading but installing from ZERO, with of course, the proper precautions that IF you have already customized your nginx.default.template file, you will need to bring those into the newer/needed https://raw.githubusercontent.com/esmero/archipelago-deployment-live/refs/heads/1.6.0/config_storage/nginxconfig/template/nginx.conf.template.anubis which needs to be used as replacement. If unsure. Don't install/upgrade to Anubis.
Ok. Done with the Notes.
If you have not already, navigate to deploy/ec2-docker and run:
docker-compose down
Then open your docker-compose.yml file and with one of the previous links open, edit the corresponding service definitions EXCEPT SOLR (we have a different guide, we told you so already!):
nano docker-compose.yml
Save your changes.
Step 2: docker pull and check
Time to fetch the latest branch and update our docker compose and composer dependencies. To pull the images and bring up the ensemble, run:
docker compose pull
docker compose up -d
Give all a little time to start. Please be patient. To ensure all is well, run (more than once if necessary) the following:
docker ps
You should see something like this if you synced all containers to the latest (your versions, nginx choice and database might vary depending on your server's platform):
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f61b89c09e4f esmero/nginx-bot-blocker:1.6.0-multiarch "/docker-entrypoint.…" 2 days ago Up 2 days 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp esmero-web
034387564ff9 esmero/php-8.3-fpm:1.5.0-multiarch "docker-php-entrypoi…" 2 days ago Up 2 days 9000/tcp esmero-php
a2fe5539b704 esmero/esmero-nlp:1.4.2-fasttext-multiarch "/usr/local/bin/entr…" 2 days ago Up 2 days 0.0.0.0:6400->6400/tcp, :::6400->6400/tcp esmero-nlp
999f73fafe89 solr:9.10.0 "docker-entrypoint.s…" 2 days ago Up 2 days 0.0.0.0:8983->8983/tcp, :::8983->8983/tcp esmero-solr
e8be343195ba minio/minio:RELEASE.2022-06-11T19-55-32Z "/usr/bin/docker-ent…" 2 days ago Up 2 days 0.0.0.0:9000-9001->9000-9001/tcp, :::9000-9001->9000-9001/tcp esmero-minio
dc27bc676166 docker:cli "docker-entrypoint.s…" 2 days ago Up 2 days ec2-docker-unhealthy_container_restarter-1
90b422544bc8 mariadb:10.6.24-jammy "docker-entrypoint.s…" 2 days ago Up 2 days 3306/tcp esmero-db
46376862f689 redis:6.2-alpine "docker-entrypoint.s…" 2 days ago Up 2 days esmero-redis
be01ebfe847c esmero/cantaloupe-s3:6.0.5-noturbojpeg-multiarch "sh -c 'java -Dcanta…" 2 days ago Up 2 days (healthy) 0.0.0.0:8183->8182/tcp, :::8183->8182/tcp esmero-cantaloupe
Important here is the STATUS column. It needs to be a number that goes up in time every time you run docker ps again (and again).
Need help? Blue Screen? Missed a step? Need a hug or someone that listens to you in silence?
If you see any issues or errors or need help with a step, please let us know (ASAP!). You can either open an issue in this repository or use the Google Group or ping us in Slack. We are here to help.