Current Drupalfilter usage is from 7.13 (2014) should be 7.19 from April of 2017

https://github.com/Islandora/islandora_drupal_filter/releases

Dockerfile has been updated and to be tested. Update documentation once testing completes.

Documentation change requests from an ISLE install test on December 19, 2017, on a new vm:

• CentOS Linux release 7.4.1708 (Core)

This section of documentation tweaks is from this URL:

• https://islandora-collaboration-group.github.io/ISLE/1_system_process_overview/1_4_testing/host_server_setup_centos/

1. DOC: adduser islandora (with password isle2017)
   CORRECTION: must also state how to set password!
   Existing text: adduser islandora (with password isle2017)
   add code format:
   adduser islandora
   passwd islandora
   isle2017

2. DOC: Create Docker group groupadd docker
   RESULT: groupadd: group 'docker' already exists

3. DOC: Add islandora user to wheel grop sudo usermod -aG wheel islandora
   TYPO: grop = group, right?

4. DOC: Exit out of the ssh session from the host server as the root user and shell back in as islandora
   SUGGESTION: Break this into two statements:
   Exit out of the ssh session from the host server as the root user
   exit
   SSH into host server as
   islandora

5. SUGGESTION: At very extreme end of "1.4. -Testing - Host Server Build - Centos" (and the other flavors, do this too), put an instruction (and hyperlink) to return to the "1.4. -Testing - Alpha Quickstart Guide"

https://islandora-collaboration-group.github.io/ISLE/1_system_process_overview/1_4_testing/alpha_quickstart/

6. DOC: The instruction that follows is confusing, as the quickstart guide never says when to run this command, only when not to run it.
   DO NOT RUN docker-compose up -d during the initial install process
   RESULT: initially, while counter-intuitive, I opted to not run any containers! That's not the result we want from that warning message above.

7. DOC: docker pull islandoracollabgroup/isle-mysql
   RESULT: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /usr/share/perl/5.24.1/Locale/Codes/Language_Codes.pm: no space left on device

8. DOC: docker pull islandoracollabgroup/isle-fedora
   RESULT: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /usr/share/perl/5.24.1/Locale/Codes/Language_Codes.pm: no space left on device

9. DOC: docker pull islandoracollabgroup/isle-apache
   RESULT: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libjfxwebkit.so: no space left on device

NOTE: Discovered flaw in our (Williams) server setup. requested that our mount be repartition to be "/opt" instead of "/opt/isle". This will prevent running out of space on "/opt".

I'm creating a new ISLE build on my MacBook using the instructions at https://islandora-collaboration-group.github.io/ISLE/1_system_process_overview/1_4_testing/alpha_quickstart/ and all appears to be OK until running the ./install_site.sh script. There I'm getting lots of errors, one for every content model I believe, like this one...

islandora_web_archive: Did not install any objects. Could not connect to the repository. Please check the settings on the Islandora configuration page and install the required objects manually on the Solution Pack admin page.   [error]

I'm not sure what might be wrong here, but I believe I've seen the effect of this before. In a previous build, not sure where anymore, we found that many metadata forms were not present, almost as though some of the solution pack objects had not been installed.

I will continue on with this build, but am wondering if we need to insert a step into the build process to ensure that the repository is working BEFORE the solution packs are installed? If others agree, how might we implement such a check?

binary installers and jar files like gsearch and fedora will be replaced in the container code with external downloads in the proper Dockerhub style

Testing has been done and is working well on Centos 7. Please Type up CENTOS host server install instructions

For the ISLE Steering Committee to document:

I discovered today a flaw in our (Williams) initial server setup. I received a vm that allocated our 4TB of storage on a mount associated with "/opt/isle", when it should clearly be "/opt". I had not bothered to check the mount, so this fracked the install.

This mistake caused us to run out of space (obviously). We should document this very precisely to prevent others from running out of space, by having them setup their mount correctly on "/opt".

"Docker-compose YAML and YOU: How-to customize ISLE for your institution."
needs to cover mounts, and their issues. for this:

• we need a clear picture of where those are and on what containers
• keep it simple, please - keep it

"Docker-compose YAML and YOU: How-to MIGRATE your Islandora instance to ISLE [at your institution]."
simply as heck:

• here is where to mount your "fedora data folder"
• here is where to mount your "solr data" "solr schema"etc.
• webroot -> isle-web
• mysql dumps -> isle-mysql

"Why I decided to use Docker Volumes instead of Mounts using docker: letting Docker handle file systems. pros and cons."
perhaps needs to cover volumes, their use and advantages. for this:

• parse down some Docker.io information into something consumable.

This issue is also duplicated for those who would like to pull this repo and BUILD their own containers - which means you can totally still roll your institutions customization DIRECTLY into your box, no sweat! looking at @hamhpc, I heard ya!

Finding that while the views module is installed and enabled, views_ui is not. This makes Drupal views difficult to configure and use in an ISLE build. At Grinnell, and elsewhere I suspect, views is a critical element.

Please modify the site make or install scripts to include views_ui. Thanks.

Having data on volume may make it easier to get at those DB files, maybe even add your own data directly into it.

Not sure (read: highly doubt) if moving entire SQL data folders around is something to do.
May just rely on dump and import for CUSTOMIZATION. To that end: review the MySQL default init or entrypoint script - I think it will scour a folder looking for sql, sql.gz or .tar files and import.

Please review my refactor pull and see if it made sense?

See #63 #64

tagging: @Islandora-Collaboration-Group/isle-steering-committee

Djatoka is not configured properly in ISLE. This prevents the Large Images from displaying using OpenSeadragon.

That is, if one is configuring the OpenSeadragon viewer and sets the "Image Server" to "Adore-Djatoka Image Server" the location of the "Djatoka-Adore Imager Server Settings" should be this:

http://fedora:8080/adore-djatoka/resolver

not just "adore-djatoka/resolver"

Peter

Dockerhub Images taggged as:
isle-fedora 3.7.1
isle-fedora 3.8
isle-fedora 3.8.1

isle-solr 4.2
isle-solr 4.6.1
isle-solr 4.10

isle-mysql 5.5
isle-mysql 5.6

isle-apache 2.2
isle-mysql 2.4

Hi.. I'd like to suggest setting the default in the docker-compose.yml to be linux instead of macosx. So the lines:

#- ./customize/apache/site/linux_settings.php:/var/www/html/sites/default/settings.php

• ./customize/apache/site/macosx_settings.php:/var/www/html/sites/default/settings.php

should get reversed like this:

• ./customize/apache/site/linux_settings.php:/var/www/html/sites/default/settings.php
  #- ./customize/apache/site/macosx_settings.php:/var/www/html/sites/default/settings.php

Since we'll need to have special circumstances for macosx (adding /etc/hosts and change the docker-compose.yml) I'd say let the linux settings be on by default so the linux builds won't need to update the docker-compose.yml. I'd imagine most of the time we'll be doing linux in the enterprise over macosx ;-).

/usr/local/bin/gs doesn't seem to be set properly? please review.

-test for web

Had success with this on my CentOS box at home yesterday (Sunday), but no luck today at work on my CentOS 7 VM. Perhaps I've stepped in the middle of an update?

This is what the Solr build reports...

rm: cannot remove '/tmp/': Directory not empty
ERROR: Service 'solr' failed to build: The command '/bin/sh -c echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections     && cd /tmp     && wget "http://archive.apache.org/dist/lucene/solr/4.10.4/solr-4.10.4.tgz"     && tar -xvzf /tmp/solr-4.10.4.tgz     && cp -v /tmp/solr-4.10.4/dist/solr-4.10.4.war /usr/local/tomcat/webapps/solr.war     && /usr/bin/unzip -o /usr/local/tomcat/webapps/solr.war -d /usr/local/tomcat/webapps/solr/     && cp -rv /tmp/solr-4.10.4/example/solr/. /usr/local/solr/     && cp -rv /tmp/solr-4.10.4/example/lib/ext/. /usr/local/tomcat/webapps/solr/WEB-INF/lib/     && cp -v /tmp/solr-4.10.4/contrib/analysis-extras/lib/icu4j-53.1.jar /usr/local/tomcat/webapps/solr/WEB-INF/lib/     && cp -v /tmp/solr-4.10.4/contrib/analysis-extras/lucene-libs/lucene-analyzers-icu-4.10.4.jar /usr/local/tomcat/webapps/solr/WEB-INF/lib/     && rm -rf /tmp/' returned a non-zero code: 1

There is indeed some odd cruft left in /tmp. I'm going to reboot to hopefully clear /tmp and give this another go.

I'm testing the islandora install process for David Keiser-Clark on a virtualbox client running ubuntu 16.04.3. Apparently curl is not installed by default on this version of ubuntu and therefore, people may need to give the command:

apt install curl

Before running the command:

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

I can't remember if I saw this error in either the Google Cloud or Amazon Cloud services Ubuntu install that I did earlier in the week.

In case it helps, I have attached a screen capture.

I'm getting this on the latest install.....

[root@localhost ISLE]# docker-compose up -d fedora
isle-mysql is up-to-date
Creating isle-fedora ...
Creating isle-fedora ... error

ERROR: for isle-fedora Cannot create container for service fedora: invalid mode: /etc/apache2/sites-available/site.conf

ERROR: for fedora Cannot create container for service fedora: invalid mode: /etc/apache2/sites-available/site.conf
ERROR: Encountered errors while bringing up the project.

To get the IA Book Viewer to work, ISLE's setting on the "Paged Content Model" configuration page needs to be changed from

http://apache/adore-djatoka/

to

http://fedora:8080/adore-djatoka/

The following the current ISLE setting, which is wrong.

Please investigate the network command explained here:

https://docs.docker.com/compose/compose-file/compose-file-v2/#network

If updating the current v2 (only) docker-compose.yml file to v2.2 & use of syntax from the example given, would allow for Apache site installation during build

`Set the network containers will connect to for the RUN instructions during build.

build:
context: .
network: host

build:
context: .
network: custom_network_1`

Docker Compose service names have been changed to be able to be uploaded to Docker Hub properly and ensure tagging works.

As such the following services db and web have been renamed to mysql and apache respectively for better clarity on actual software used.

Additionally image names now all have islandoracollabgroup/ added as a tagging prefix.

All documentation especially build processes will need to be updated in order to ensure proper usage and builds by endusers

I found a couple things in the documentation. First this instruction:

unzip https://github.com/openseadragon/openseadragon/releases/download/v2.2.1/openseadragon-bin-2.2.1.zip

should just be:

unzip openseadragon-bin-2.2.1.zip

Then I also think that you need to put in to disable the openseadragon module first before fixing this part. when I tried to enable the module from the instructions it tells me that it was already enabled. So we're fixing openseadragon while the old module is still active. I'm sure it works fine but we might want to disable it first so the enable part works. When I did it it told me it was already enabled. Nothing major.. just a little nit-picky things =).

Can I make a request to please build 'nano' into any Linux images? My vi skills are practically non-existent and I've butchered more than one file this afternoon.

This might be a little bit simpler to set up sudo for islandora user. This is what I have been doing that works but I'm not sure if this is just a CentOS thing or sudo thing universally (meaning not sure it's the same in Ubuntu). Anyhow here's the method:

echo "islandora ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/islandora

That's it =). No messing with visudo!

(David is submitting this issue on behalf of a colleague who's testing ISLE on AWS Ubuntu 16.04)

Hello all -
I found this reference to install docker-compose on linux:
https://docs.docker.com/compose/install/#install-compose

It looks like your documentation is missing critical sing quotes which may simply be a formatting issue on your page.

Here is the command that I used to install docker-compose with the quotes in the correct places:

sudo curl -L https://github.com/docker/compose/releases/download/1.17.0/docker-compose-`uname -s-uname -m` -o /usr/local/bin/docker-compose

Hope it helps,

• Lynna

I think having a viable product takes precedent; to that end I don't believe anything in this ticket needs action now, none of this is a blocker.

Hi - I was looking through some of the Dockerfiles and had a few thoughts!

Container Level (subfolders)

I still have an overall folder structure question: would it be possible for Container folders to contain their Dockerfile, and a single consolidated folder for all configs (even if that folder has children, this is especially true on multi-daemon containers). Reading the Dockerfile it is easier to understand seeing COPY file from a config folder to a destination on the container, or a "lib" folder being copied to the lib location on the container, etc.

ISLE-MYSQL I think can be removed from the images entirely and left in the services definition. Are we maintaining a customized version of MySQL? I can totes provide an example - this is the easiest way for me.

ISLE-FEDORA is perhaps the most challenging as it might as well be called "core" and it hosts more than one daemon. The layers in this box are incredible. :jaw-drop: (needs to be a thing)

ISLE-WEB: again, lots of layers, but here we're using intermittent builds! Nice!

• organize folders in a coherent manner for their containers
• deprecate "MAINTAINER" and use LABELS per Docker.
• Can ISLE-MY be deprecated?
• network consideration (should be at the services level, Ben)

I'll update as I go but sorry, these are some of the thoughts now!

Hi.. I'm able to spin up a VM according to instructions here:

https://github.com/hamhpc/ISLE-ks/blob/master/ks_ISLE.cfg

However, since the docker service isn't running, the container building and config tweak sections (last two sections of code) of this code don't work so I run them manually.

when I run them manually the services all appear to come up properly. Everything looks good. However, when I log into the host and try to do the last parts to set up the site I keep getting an error. It would seem that my database connection settings are getting established somehow which makes it so the site won't install properly. When I browse the site, I'm taken to the drupal installation page to run through the drupal install process. Here's what I see when I run the install_site.sh script:

root@41d07d8c66f8:/tmp# ./install_site.sh 
Installing all Islandora modules
Installing Drupal Site
exception 'Drush\Sql\SqlException' with message 'Unable to find a    [error]
matching SQL Class. Drush cannot find your database connection
details.' in
/opt/drush-7.x/vendor/drush/drush/commands/sql/sql.drush.inc:597
Stack trace:
#0
/opt/drush-7.x/vendor/drush/drush/commands/core/site_install.drush.inc(109):
drush_sql_get_class()
#1 [internal function]: drush_core_pre_site_install()
#2 /opt/drush-7.x/vendor/drush/drush/includes/command.inc(361):
call_user_func_array('drush_core_pre_...', Array)
#3 /opt/drush-7.x/vendor/drush/drush/includes/command.inc(212):
_drush_invoke_hooks(Array, Array)
#4 [internal function]: drush_command()
#5 /opt/drush-7.x/vendor/drush/drush/includes/command.inc(180):
call_user_func_array('drush_command', Array)
#6 /opt/drush-7.x/vendor/drush/drush/lib/Drush/Boot/BaseBoot.php(64):
drush_dispatch(Array)
#7 /opt/drush-7.x/vendor/drush/drush/drush.php(70):
Drush\Boot\BaseBoot->bootstrap_and_dispatch()
#8 /opt/drush-7.x/vendor/drush/drush/drush.php(11): drush_main()
#9 {main}
Drush vset of Drupal Site configurations
Command variable-set needs a higher bootstrap level to run - you will[error]
need to invoke drush from a more functional Drupal environment to run
this command.
The drush command 'vset islandora_paged_content_djatoka_url          [error]
http://apache/adore-djatoka/' could not be executed.
Drush was not able to start (bootstrap) the Drupal database.         [error]
Hint: This may occur when Drush is trying to:
 * bootstrap a site that has not been installed or does not have a
configured database. In this case you can select another site with a
working database setup by specifying the URI to use with the --uri
parameter on the command line. See `drush topic docs-aliases` for
details.
 * connect the database through a socket. The socket file may be
wrong or the php-cli may have no access to it in a jailed shell. See
http://drupal.org/node/1428638 for details.

Drush was attempting to connect to: 
 Drupal version         :  7.56                                     
 Site URI               :  http://default                           
 PHP executable         :  /usr/bin/php                             
 PHP configuration      :  /etc/php/5.6/cli/php.ini                 
 PHP OS                 :  Linux                                    
 Drush script           :  /opt/drush-7.x/vendor/drush/drush/drush. 
                           php                                      
 Drush version          :  7.4.0                                    
 Drush temp directory   :  /tmp                                     
 Drush configuration    :                                           
 Drush alias files      :                                           
 Drupal root            :  /var/www/html                            
 Site path              :  sites/default    

Any ideas what I'm doing wrong?

Can I make a request to please build 'emacs' into any Linux images? If having nano/vi/emacs is problemsome, I can get out a cheatsheet for nano or vi, but emacs is my editor of choice and I'm all thumbs with the others.

Hi.. I worked out this sed command to update /etc/hosts in CentOS 7. It might be easier to have in the documentation to do this than to have to explain how to do it in an editor. Plus helpful when those want to do scripted installs if we can come up with methods that help facilitate that.

sed -i 's|127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4|127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4\n127.0.0.1 islandora-docker.com fedora.islandora-docker.com apache.islandora-docker.com fedora apache|g' /etc/hosts

This is also a little different in that I'm adding a second 127.0.0.1 line after the localhost line to contain the ISLE names. This way they won't mess with their primary localhost entry for their OS.
So the end result is this:

[root@islandora-dev ISLE]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
127.0.0.1 islandora-docker.com fedora.islandora-docker.com apache.islandora-docker.com fedora apache
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
[root@islandora-dev ISLE]#

Documentation change requests

Documentation change requests from an ISLE install test on December 21, 2017, on a new vm:

• CentOS Linux release 7.4.1708 (Core)
  This section of documentation tweaks is from this URL:

• https://islandora-collaboration-group.github.io/ISLE/1_system_process_overview/1_4_testing/host_server_setup_centos/

1. If your institution's server uses real DNS, then you can skip this step:
   "Open up a terminal and enter: sudo vi /etc/hosts"

2. When turning on the fedora container, the pretty green "done" text is listed one time, but the declarative "Creating isle-fedora ... " is listed twice. It needs a second "done" statement, or remove the second "Creating isle-fedora ... " statement.
   [islandora@isle-dev ISLE]$ docker-compose up -d fedora
   Creating isle-fedora ... done
   Creating isle-fedora ...

3. Similar issue as #2, above for "apache" container:
   [islandora@isle-dev ISLE]$ docker-compose up -d apache
   Creating isle-apache ... done
   isle-fedora is up-to-date
   Creating isle-apache ...

4. The final bullet in "5. Install script on Apache container (20 - 40 mins)" deserves to have it's own bullet. Additionally, we should add some text like

• QC the resulting setup by reviewing the web address for your new Islandora Docker server (i.e. http://myname.institution.edu)

5. QC'ing the resultant website: Yea, the website exists!

Typing the correct admin username (islandora_docker_admin) and pwd results in this error message:

• http://islandora-docker.com/node?destination=node
• Not Found
• The requested URL /node was not found on this server.
• Apache/2.4.29 (Ubuntu) Server at islandora-docker.com Port 80

THE PROBLEM is that the homepage submit button on my site (http://isle-dev.williams.edu/) is redirecting to this other site (http://islandora-docker.com/node). I never changed my /etc/hosts file, so I believe that the ISLE installation should not know about islandora-docker.com at all.

looking around to see if there are any real sites or recommendations for data integrity at the bit level for IR.

@hamhpc do you have thoughts on this? Am I doing overthink? In your experience have you dealt with bit rot and is this something? With RHEL deprecating btrfs are there implications? Do RHEL and derivs have z4l baked in (guess: no)?

This is out of scope but should be considered as a best practice document if it does not exist somewhere else.

using a temporary linux server on Digital Ocean to weed out the Docker-for-Mac specific issues to get the containers able to run on a linux environment

ISLE Steering Committee testers will be given access to this server

1. When turning on the fedora container, the pretty green "done" text is listed one time, but the declarative "Creating isle-fedora ... " is listed twice. Ideally, only show a single output of "Creating isle-fedora ... done"; if that's not possible, then at least add the word "done" following the second "Creating isle-fedora ... " statement:
   [islandora@isle-dev ISLE]$ docker-compose up -d fedora
   Creating isle-fedora ... done
   Creating isle-fedora ...

2. Similar issue as #2, above for "apache" container:
   [islandora@isle-dev ISLE]$ docker-compose up -d apache
   Creating isle-apache ... done
   isle-fedora is up-to-date
   Creating isle-apache ...

3. Typing the correct admin username (islandora_docker_admin) and pwd results in this error message:

• http://islandora-docker.com/node?destination=node
• Not Found
• The requested URL /node was not found on this server.
• Apache/2.4.29 (Ubuntu) Server at islandora-docker.com Port 80

THIS HAPPENS BECAUSE: the homepage of my newly installed site (http://isle-dev.williams.edu/) has a "submit" button that is redirecting to http://islandora-docker.com/node.
NOTE that I had not changed my /etc/hosts file; I believe that the ISLE installation should not know about islandora-docker.com at all. There must still be a lingering reference somewhere, right?

Bumped into this when spinning up ISLE on my MacBook for the first time...

ma7053:ISLE markmcfate$ docker-compose up -d solr
isle-solr is up-to-date

ma7053:ISLE markmcfate$ docker-compose up -d web
isle-db is up-to-date
isle-fedora is up-to-date
Starting isle-web ... 
Starting isle-web ... error

ERROR: for isle-web  Cannot start service web: driver failed programming external connectivity on endpoint isle-web (43d6722e4ca307484e2a6ce220fb139ba623470756f88b60e06d329ff1c800fd): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure EADDRINUSE)

ERROR: for web  Cannot start service web: driver failed programming external connectivity on endpoint isle-web (43d6722e4ca307484e2a6ce220fb139ba623470756f88b60e06d329ff1c800fd): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure EADDRINUSE)
ERROR: Encountered errors while bringing up the project.

I'm looking into potential conflicts with port 80 now.

Sorry to keep making requests.

I'm working with my local instance of Isle-web and am trying to setup IMI (Islandora Multi Importer) in order to help quickly populate some objects in my test repo. But rsync is not installed on the image? I thought it was standard linux fare, but apparently it is not.

I've just installed it from my bash terminal (sudo apt-get install rsync) and am running an rsync now. Could we possibly add rsync to the image in the future to eliminate this step? Thanks.

-test for Fedora
-test for Solr

Hi,
I was wondering what the root password is for the host? I see in the matrix that under the MySQL container there is this:

root | islemysqlrootpw2017

I suspect this might also be the root password for the host? Not a big deal as using my kickstart method you can set the root pass when the machine is built (from the configure OS screen). I was just looking for what might have been set already as I would grab that encrypted password and set it in the kickstart script so that it matches up with the matrix.

I think having a viable product takes precedent; to that end I don't believe anything in this ticket needs action now, none of this is a blocker.

Hi - I was looking through the services.yml and had a few thoughts I'd like to share to the group

I believe because of how large this stack is the naming and organization of the enduser config and data folders ("customize" currently) need to be clearer than they are now. As an admin who wants to import their site: where is the mysql data folder, drupal data folder, fedora, solr, etc.? where would I place my config files to override the ISLE defaults for any of those daemons?

the 'data' folder - any data we want to persist. Should we consider using Docker volumes in consideration of moving and migrating, or replicating?

Services Level (the folder with the Docker-compose.yml)

• Could we rename the "Customize" folder to either "Config" or "Data" depending on it's role?
• do those files fit into either a "config" or a "data" role?
• is it at all possible to squash down some of the volumes definitions? e.g.:

    - ./customize/fedora/tomcat/server.xml:/usr/local/tomcat/conf/server.xml
    - ./customize/fedora/tomcat/web.xml:/usr/local/tomcat/conf/web.xml
    - ./customize/fedora/tomcat/tomcat-users.xml:/usr/local/tomcat/conf/tomcat-users.xml
    - ./customize/fedora/tomcat/logging.properties:/usr/local/tomcat/conf/logging.properties

to ./customize/fedora/tomcat:/usr/local/tomcat/conf or would that break things?

I also hope this highlights my confusion with a folder named 'customize' as you see it's a conf folder. Maybe I'm thinking to far into it!

Best!

I got my containers running on my MacBook and attempting the final "step", the ./install_site.sh portion of...

docker exec -it isle-web bash
cd /tmp
chmod 777 *.sh
./make_site.sh
./install_site.sh

...but I run into a bunch of these:

Command pm-enable needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command.                                  [error]
The drush command 'en islandora_basic_collection' could not be executed.

This appears to have precipitated a number of other errors down the line. I also tried 'cd /var/www/html/sites/default' and running /tmp/install_site.sh but with the same results.

Perhaps we need to define a Drush alias, like @default, and invoke the drush commands using it?

I'm running through the centos instructions and so far they seem to work fine. When I get to the apache container I get this:

[islandora@islandora-dev ISLE]$ docker-compose build apache
Building apache
Step 1 : FROM ubuntu:14.04 AS ffmpeg_base
ERROR: Service 'apache' failed to build: Error parsing reference: "ubuntu:14.04 AS ffmpeg_base" is not a valid repository/tag
[islandora@islandora-dev ISLE]$

In the Islandora install documentation at:
https://islandora-collaboration-group.github.io/ISLE/1_system_process_overview/1_4_testing/alpha_build_guide_linux/

In the section called "Clone ISLE repository"
You have people "cd opt" did you mean "cd /opt" instead ?????

A command a few lines down from this --- " cd /opt/ISLE"
seems to imply you want the above command to actually be:

cd /opt

(I assume you know this but in case you don't --- Without the slash in front of the "opt" the cd command will land in a "opt" directory one below the current directory. With the slash in front of "opt" the cd command will land in the opt directory at the root of the system drive.)

Issue not reproducible in other Host types

• Tested on a Vagrant / Virtualbox Ubuntu 16.04 VM Host on a MacOS
• Tested on a remote Digital Ocean server droplet running Ubuntu 16.04 LTS as the ISLE Host
• It did not manifest on any of the previous Alpha work (so far)

When testing the new alpha2 ISLE Docker images, on a local MacOS laptop running Docker For Mac, Fedoragsearch refuses to start in Tomcat on the isle-fedora` container.

All other containers work properly, even the installation of the Drupal site.

The only clue is within the Fedora container's tomcat logs, local_host_access.datetimestap.log

07-Feb-2018 20:39:17.563 SEVERE [http-nio-8080-exec-3] org.apache.catalina.core.StandardContext.filterStart Exception starting filter XmlUserfileFilter
java.lang.StackOverflowError
    at java.util.Hashtable.containsKey(Hashtable.java:336)
    at org.apache.log4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:36)
    at org.apache.log4j.LogManager.getLogger(LogManager.java:39)

org.apache.catalina.core.StandardContext.filterStart Exception starting filter EnforceAuthnFilter
java.lang.NoClassDefFoundError: Could not initialize class org.fcrepo.server.security.servletfilters.FilterSetup
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:151)

My suspicion is how Docker For Mac handles the networking for localhost .

I did attempt to edit any value with localhost in the Fedoragsearch config files, swapping out localhost with fedora for all SOAP call related entries but to no avail as the app wouldn't start.

I wonder if there is an issue with access to Fedora by Fedoragsearch given the Could not initialize class org.fcrepo.server.security.servletfilters.FilterSetup entry however I don't have enough information at this time to proceed.

Is it possible that Fedora doesn't see the calls from Fedoragsearch to its repo as coming from the isle-fedora localhost and instead as something to be blocked by XACML or Spring (web.xml)/ filter ?

Posting this issue here for others to test.

Please note: MacOS users have a documented alternative method of using Vagrant and Virtualbox to host isle.localdomain locally on their laptops /workstations.

Hi,

ISSUE

One the issues with current FITS (1.2.0) it that it during the TECHMD generation Apache Tika is executed on Binaries resulting in huge/large amount of temporary file(s), much larger than original datastreams that are checked againts. This can lead, on large ingest sets to temporary out of space situations. Normal /tmp cleanup routines found on Ubuntu are not able to deal with this files.

Filenames start with apache-tika

The simples fix is to comment this line

at /usr/local/fits-1.2.0/xml/fits.xml

<!--  Comment tika processing or your /tmp file will fill up sooo fast!
          <tool class="edu.harvard.hul.ois.fits.tools.tika.TikaTool" exclude-exts="jar,avi,mov,mpg,mpeg,mkv,mp4,mpeg4,m2ts,mxf,ogv,mj2,divx,dv,m4v$
 -->

This has issue has been replicated by Samvera users/DGI and Metro (all with different levels of frustration)

Omit the warning message at will.

HOW TO REPLICATE

Execute any derivative regeneration on Objects where TECHMD processing is enabled. Look at your /tmp folder for apache-tika files.

The subject project/script is only about 1/3 complete (estimate) but I think having a tool like this, or some equivalent outcome, would be a welcome addition to ISLE. Perhaps the 'docker-compose up' process itself can "harvest" and report version info as containers are instantiated?

Please update FITS on the web container from 1.04 to 1.20

As of Aug 2017 https://projects.iq.harvard.edu/fits/news/fits-120-released

Ensure that logging is separate with INFO only.

Remove "1st and last steps" to get generic website going

Within Dockerfile for web

• Include running drupal and islandora makefiles process too. Copy contents to web folder?
• Test impact on customization folder. Is this overwritten?
• Add drush.sh contents and ensure shelling / PDW works

Docker has a few suggests, but I like WAIT FOR IT... wait-for-it.sh

https://github.com/vishnubob/wait-for-it

Could that before fedora to wait for mysql defeat race?

tagging @g7morris

Change sample URL from islandora-docker.com to:

• isle.local
• isle.dev
• ? (other)

This should be decided during the ISLE Steering Committee call on 12/1/2017 prior to implementation.

Running Ubuntu 16.04.3 in VirtualBox 5.2.2 on Mac OS 10.12.6 ...

docker-compose up -d fedora
returns an error of "Cannot create container for service fedora: invalid bind mount spec ..."

See attached screen shot for complete error

I definitely did not have this error when building this on the google cloud compute service.