Error on "docker-compose down"

[wpwen...@gmail.com]

ERROR:

        Can't find a suitable configuration file in this directory or any

        parent. Are you in the right directory?

        Supported filenames: docker-compose.yml, docker-compose.yaml

Interesting. After approx 53 days of uptime, I'm needing to take down the instance to troubleshoot IIF not resolving our JP2s, and I can't take down the instance. Any thoughts as to why I'm getting this error? I was able to bring up the instance, not sure why I can't bring it down now...

Thanks,
Paul

[William Matheson]

Hi Paul,

What do you see if you run a file listing? Also you might want to make sure you have a .env file that among other things specifies your actual COMPOSE_FILE (e.g. docker-compose.production.yml). IIRC there was something changed with regards to tracking that file and I had to copy mine back in from a previous copy.

WM

[wpwen...@gmail.com]

Hi William,

Here's our directory listing:

Our "sample.env" contains the actual COMPOSE_FILE reference to "docker-compose.production.yml" per the new tracking method (since .env is no longer tracked). I'm wondering if just copying the sample.env to another file named .env would do the trick....

I'm a bit confused how I was able to "up" the instance, but am no longer able to take it down...

[wpwen...@gmail.com]

Copying sample.env to .env did it! Thanks, William! 

On Monday, August 24, 2020 at 11:34:49 AM UTC-5 William Matheson wrote:

[brandonw]

Did you make any changes to your yml files before bringing them down? If so, you'll need to revert, being them down, and then make your changes. 

--
You received this message because you are subscribed to the Google Groups "Islandora ISLE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora-isl...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/islandora-isle/a1454c0d-0d8b-465f-829f-697ec4ce179dn%40googlegroups.com.

[William Matheson]

Mysteries of the universe, perhaps. Somebody might be able to come up with a better answer, but in the meantime yeah, you could probably reconstruct your .env from the sample.env format, or one of the other examples. Documentation is available here: https://islandora-collaboration-group.github.io/ISLE/install/install-environments/

[wpwen...@gmail.com]

Yeah, simply copying the sample.env to .env was what brought it back. I seem to remember we had this problem in 1.4.2 and it was fixed by just copying that .env back over, but it's hard to keep up with all the little tweaks to the versions that happen along the way. I think when we upgraded from 1.4.2 to 1.5.0 the .env was lost again, hence the issue. Thanks for the reminder about the .env change, William!

[Brandon Weigel]

 I seem to remember we had this problem in 1.4.2 and it was fixed by just copying that .env back over, but it's hard to keep up with all the little tweaks to the versions that happen along the way. I think when we upgraded from 1.4.2 to 1.5.0 the .env was lost again, hence the issue. 

At some point in recent history, .env was removed from the Git repository and added to .gitignore so that updates would no longer overwrite your .env, but I found that the quirks of Git mean you end up deleting your own .env the first time you pull in the update. It shouldn’t be a problem in future updates though (I think).

Brandon Weigel
Coordinator and Arca Manager
BC Electronic Library Network
Phone: 604.401.1794
Email: bran...@bceln.ca
Web: https://bceln.ca, https://arcabc.ca

-- 
You received this message because you are subscribed to the Google Groups "Islandora ISLE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora-isl...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/islandora-isle/1f8bb191-9e92-437c-b0c7-604411c7fc01n%40googlegroups.com.