[GemStone-Smalltalk] GemStone in docker container

[David Shaffer]

Sounds good:

https://hub.docker.com/repository/docker/cdavidshaffer/gemstone <https://hub.docker.com/repository/docker/cdavidshaffer/gemstone>

Let me know if you would like any changes to the verbiage.  The only key files in this image are the ones included in the GemStone zip file.  Comments, questions and contributions are welcomed.

I’m curious how GemStone handles the “exit by crashing” approach that is typical of docker containers.  Will it try to replay transaction logs when it starts back up?  BTW, it isn’t clear in the docker documentation what happens to processes in a container when it’s “main process” terminates.  In the case of my gemstone container, the “main process” is just a sleep command.  Maybe it would be better to run the stone in the foreground (is that possible) so that docker will send it SIGKILL and it can deal with a proper shutdown?

David

> On Nov 5, 2019, at 5:35 PM, James Foster <Smalltalk at JGFoster.net> wrote:
> 
> Hi David,
> 
> Nice to see some work on GemStone in Docker!
> 
> See below…
> 
>> On Nov 5, 2019, at 1:03 PM, David Shaffer via GemStone-Smalltalk <gemstone-smalltalk at lists.gemtalksystems.com <mailto:gemstone-smalltalk at lists.gemtalksystems.com>> wrote:
>> 
>> Hi folks,
>> 
>> I’m recently making my way back to GemStone after many years away.   As James Foster has suggested, it wasn’t difficult to get GemStone working in docker but I thought I’d provide a resource for people who are interested:
>> 
>> https://github.com/cdavidshaffer/gemstone-docker <https://github.com/cdavidshaffer/gemstone-docker>
>> 
>> So far I find it quite nice to have a “GemStone” appliance.  I’d like to put the gemstone docker image on docker hub but I’ll need to confer with GemTalk first.
> 
> While I’m happy to discuss any specific concerns privately, I’ll say that you may redistribute GemStone subject to the following conditions:
> you don’t include any keyfile other than the “Starter Edition” keyfile that ships with the distribution (don’t distribute your keyfile);
> you specify that use is subject to the License Agreement found at https://downloads.gemtalksystems.com/pub/GemStone_License_Agreement.pdf <https://downloads.gemtalksystems.com/pub/GemStone_License_Agreement.pdf>; and 
> you state clearly that this is not an official GemTalk Systems LLC release, but your independent repackaging.
> Beyond that, we welcome efforts to make GemStone easier to deploy. Does that seem reasonable?
> 
> James Foster
> VP of Finance and Operations
> GemTalk Systems LLC
> +1 503 766 4714
> James.Foster at GemTalkSystems.com <mailto:James.Foster at GemTalkSystems.com>
> 
>> I tried to provide some “help” text in the repository Readme but I’m just getting re-acquainted with GemStone so it is likely to take a while before I can provide more useful advice (back-ups and other important system admin chores are completely missing from my description).
>> 
>> I’m running an AWS ECS instance with GemStone now and plan to provide instructions for getting started on that platform as soon as I’m sure my database is stable.
>> 
>> Comments, corrections and criticisms are always welcome!
>> 
>> Best,
>> 
>> David
>> 
>> _______________________________________________
>> GemStone-Smalltalk mailing list
>> GemStone-Smalltalk at lists.gemtalksystems.com <mailto:GemStone-Smalltalk at lists.gemtalksystems.com>
>> https://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gemtalksystems.com/mailman/private/gemstone-smalltalk/attachments/20191106/92421687/attachment-0001.htm>