If I go:
Code: Select all
docker run -it dyalog/dyalog
I get an interactive session. I don't need an interactive session but it's a good way to experiment. If in the session I try and use any user-defined command I get this:
Code: Select all
_______ __ _ ____ _____
| __ \ \ / //\ | | / __ \ / ____|
|_| | \ \_/ // \ | | | | | | |
| |\ // /\ \ | | | | | | | _
____| | | |/ / \ \| |___| |__| | |__| |
|_____/ |_/_/ \_\______\____/ \_____|
https://www.dyalog.com
*************************************************************************************
* This software is for non-commercial evaluation ONLY *
* https://www.dyalog.com/uploads/documents/Private_Personal_Educational_Licence.pdf *
*************************************************************************************
Dyalog APL/S-64 Version 17.1.36845 Unicode
For i86_64
Created: Aug 15 2019 at 00:13:45
Copyright (c) Dyalog Limited 1982-2019
]???
VALUE ERROR: Undefined name: ⎕SE.UCMD
Yet the files with the commands are all there:
Code: Select all
)sh find / -name '*.dyalog'
find: ‘/root’: Permission denied
find: ‘/var/cache/apt/archives/partial’: Permission denied
find: ‘/var/cache/ldconfig’: Permission denied
/opt/mdyalog/17.1/64/unicode/Library/Core/APLProcess.dyalog
/opt/mdyalog/17.1/64/unicode/Library/Core/Tool.dyalog
/opt/mdyalog/17.1/64/unicode/Library/Conga/HttpCommand.dyalog
/opt/mdyalog/17.1/64/unicode/Library/Conga/HttpUtils.dyalog
/opt/mdyalog/17.1/64/unicode/Library/Conga/InitConga.dyalog
/opt/mdyalog/17.1/64/unicode/Library/Conga/FtpClient.dyalog
/opt/mdyalog/17.1/64/unicode/PublicCACerts/Export.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Link/Deserialise.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Link/Serialise.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Link/Install/WSLoaded-default.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Link/Install/RemoveLinks.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Link/Install/WSLoaded-clean.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Link/Install/BUILD_DYALOGSPACE.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Link/Test.dyalog
/opt/mdyalog/17.1/64/unicode/StartupSession/Dyalog/Serial.dyalog
/opt/mdyalog/17.1/64/unicode/SALT/core/Utils.dyalog
/opt/mdyalog/17.1/64/unicode/SALT/core/SALTUtils.dyalog
/opt/mdyalog/17.1/64/unicode/SALT/core/Parser.dyalog
/opt/mdyalog/17.1/64/unicode/SALT/core/UnicodeFile.dyalog
/opt/mdyalog/17.1/64/unicode/SALT/core/SALT.dyalog
[...]
Is this an oversight? The same applies to dyalog/dyalog:17.1.
Should I try a different image?
EDIT: dyalog/dyalog:17.1-dbg seems to work. I spent a few minutes trying to understand the difference, but I don't see it.