@drkameleon: you wrote: "That being said, you're more than welcome to post all issues you come across, related to... anything."
=>Therefore ;-) :
When i run "docker run -it arturolang/grafito" from windows 11 pro & docker commandline <docker run -it arturolang/grafito>, the container is fetched correctly and built, but when it starts grafito, i get the following response (right after the Grafito-logo):
`
Runtime | dictionary key not found: engine
error | perhaps you meant...
`.
Same happens in WSL2.

Possible cause:
Seems to me it is not assigning the engine field in the Versions dict correctly?
i assume the sqlite3 --version returns something faulty within the docker?
and indeed, from within arturo in the docker, i get this response:
$> execute "sqlite3 --version"
=> /bin/sh: sqlite3: not found
Or extended:
$> to :version first split.by:" " execute "sqlite3 --version"
Runtime | cannot convert argument: "/bin/sh:"
error | from :string
| to :dictionary
@drkameleon: you wrote: "That being said, you're more than welcome to post all issues you come across, related to... anything."
=>Therefore ;-) :
When i run "docker run -it arturolang/grafito" from windows 11 pro & docker commandline <docker run -it arturolang/grafito>, the container is fetched correctly and built, but when it starts grafito, i get the following response (right after the Grafito-logo):
`
Possible cause:
Seems to me it is not assigning the engine field in the Versions dict correctly?
i assume the sqlite3 --version returns something faulty within the docker?
and indeed, from within arturo in the docker, i get this response:
$> execute "sqlite3 --version"
=> /bin/sh: sqlite3: not found
Or extended:
$> to :version first split.by:" " execute "sqlite3 --version"