offline installation openrem 1.0

[jaap....@gmail.com]

I'm trying to install openrem v1.0 on an offline system in our hospital. Offline installation of docker and docker-compose was a succes. And getting all the openrem images was not that difficult thanks to clear instructions. However, when trying to fire up all containers with docker-compose, I hit a barrier. Docker-compose wants to check whether my images are the latest or not, by checking the docker registry. But the system is offline, thus resulting in a timeout error. 

Any suggestions of how I could handle this?

I already tried docker-compose pull --ignore-pull-failures first, but that doesn't work.

Best, Jaap

[Ed McDonagh]

Sorry Jaap, I forgot to come back to you.

Does docker-compose attempt to check for the latest image when you issue the "docker-compose up -d" command? I didn't think it did - I thought it just did that when you use the pull command.

--
You received this message because you are subscribed to the Google Groups "OpenREM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrem+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/openrem/8c0c820a-27de-490c-be3c-2c92337c242en%40googlegroups.com.

[jaap....@gmail.com]

Hi Ed,

No problem and yes that is exactly what happens unfortunately. I saw a few posts (on stackoverflow I think) suggesting we should do something with the tag of the images, but haven't been able to try that.

Best, Jaap

Op donderdag 13 januari 2022 om 09:56:02 UTC+1 schreef Ed McDonagh:

[Ed McDonagh]

Ok, I'll have to mock it up and see what happens. If anyone else can chip in, please do!

David Platten - didn't you try this too?

To view this discussion on the web, visit https://groups.google.com/d/msgid/openrem/c6edcba3-eaa8-4af1-a962-76d210ac0836n%40googlegroups.com.

[jaap....@gmail.com]

I asked the IT department to open the firewall so I could install. It seems only the nginx container needs internet access (it's pulling), the rest does not.

So maybe we need a different image for the nginx?

Op donderdag 13 januari 2022 om 10:02:54 UTC+1 schreef Ed McDonagh:

[Ed McDonagh]

I don't see why it would. Do you think it could be because it is an old tag - 1.17? Maybe go to the current stable version, so change the image in docker-compose being nginx:stable instead of 1.17.8-alpine. Or maybe stable-alpine to keep it small.

You'd obviously need to be able to download it the once...

To view this discussion on the web, visit https://groups.google.com/d/msgid/openrem/b6698328-8cf7-4719-b0c4-1e7397ea01fen%40googlegroups.com.