Closed arni-magnusson closed 8 months ago
If on a linux host, use command below to tun in the container
docker run --rm --volume $PWD:/simple --workdir /simple --entrypoint ./simple johnoel/admb-13.2:linux
Right, that's the "host-level call" that I mentioned, which ran without problems. I guess I'm trying to make two points:
The lines
For Linux host, executable could be run locally.
./simple
can perhaps be deleted from the quickstart-unix tutorial, if the statement is not generally true. It seems to me that the user cannot run the executable locally unless their host machine (laptop) happens to be Debian 12, matching the basis of the image.
Alternatively, the above lines could stay in the tutorial if we are indeed able to guarantee that the model executable can run on practically all Linux machines (Red Hat, openSUSE, etc.). I don't know enough about statically linked executables to know if such executables are achievable or recommended. I would be happy to see the lines deleted from the tutorial if the executable cannot be run locally by typing ./simple
in the host terminal.
Is the -p
(for portable) option still relevant as discussed here: https://github.com/admb-project/admb/pull/127?
Hi! I just ran the tutorial QuickStart - Using ADMB Docker Linux Image with success on an Ubuntu 22.04 host. Happily built and ran simple.tpl, first as a host-level call and then as an interactive session. Great improvement since the previous container release.
The only question I have is where it says
In my case that returns an error message
Do we know if the model executable was built statically, and whether that could be helpful for running the executable locally on the host machine without getting an error message?