You ca look here for inspiration:


On 9 Aug 2023, at 13:55, Guillermo Polito <guillermopol...@gmail.com> wrote:

Hi @Philippe,

this is too few info to help, but maybe you can try the following:

 - are you sure the image inside the container and outside are the same version? => what if you use the same version outside the docker file?
 - the issue happens because of a deprecation exception, what if you disable them through the settings (there is a programmatic way to do it)?

G

El 1 jul. 2023, a las 09:28, p...@pt.lu escribió:

Hello,

I am trying to run TinyBlog and Pharo in a Docker container.  It run, but it crashes after a while with the following log:

pva@dd8:~/docker/PharoTinyBlogDocker$ docker logs --tail 1000 b5172118c19f
ZnZincServerAdaptor
DeprecationPerformedNotification: Automatic deprecation code rewrite: The method MAContainerComponent>>#isReadonly called from TBSMagritteFormRenderer>>#renderElement: has been deprecated. Use #isReadOnly instead.
DeprecationPerformedNotification: Automatic deprecation code rewrite: The method MADescriptionComponent>>#isReadonly called from TBSMagritteCheckboxComponent>>#renderEditorOn: has been deprecated. Use #isReadOnly instead.
SmalltalkImageInstanceID class>>startUpSyntax Error on line 1: 'Variable or _expression_ expected'
=========================================================
1: `@receiver readonly:
                      _^_
SmalltalkImageInstanceID class>>startUpSyntax Error on line 1: 'Variable or _expression_ expected'
=========================================================
1: `@receiver readonly:
                      _^_
ZnZincServerAdaptor

I have tried to fix the problem in a regular image and it does not behave the same.

Is there a way to debug graphically the Pharo located in the docker file ? I did not find any resources on the net concerning this kind of configuration.

Thanks in advance for your help,

Philippe Vanderheyden




--
Cordialement,
Philippe

Philippe Vanderheyden
Rue Maria Teresa, 15
L-8448 Steinfort
T: 77 07 66
G: 621 365 901
<pvdh.vcf>

Reply via email to