Hello,
I read fine-tuning-the-configuration, but got some issues:
1.: I can get the copied configuration fileto the / thats ok.
Do you mean on the host or in the container?
If it is on the host, you need to bindmount it using `docker run --
volume ...`. If it is in the container (e.g. you used `docker cp`) you
need to make sure it is copied every time you run it as the topmost
read/write layer is not persistent when you recreate the container
unless you commit it using `docker commit`. Use `docker build` and a
Dockerfile with a COPY directive to simplify the process (create
container, copy file in topmost layer, commit it to create new image
with configuration that you can run).
2.: I can stop Orthanc with this command:
root@jodogne-orthanc1:/# Orthanc stop
W0607 06:27:49.323275 main.cpp:1238] Orthanc version: 1.2.0
E0607 06:27:49.326712 OrthancInitialization.cpp:203] Inexistent path
to configuration: stop
E0607 06:27:49.326957 main.cpp:1264] Uncaught exception, stopping
now: [Inexistent file] (code 13)
W0607 06:27:49.327681 main.cpp:1297] Orthanc has stopped
Is that inside the container? In general you should never need to
control a container using a process inside it (shell or otherwise); in
fact a container is usually just one process.
Please try using the various docker commands from the host.
docker start $container
docker stop $container
docker restart $container
docker run $container
docker rm $container
3.: I can't restart the Orthanc anymore and got this message:
root@jodogne-orthanc1:/# Orthanc ./Configuration.json
W0607 06:27:54.787362 main.cpp:1238] Orthanc version: 1.2.0
W0607 06:27:54.790501 OrthancInitialization.cpp:125] Reading the
configuration from: "./Configuration.json"
W0607 06:27:54.793391 FromDcmtkBridge.cpp:141] Loading the external
DICOM dictionary "/usr/share/libdcmtk2/dicom.dic"
W0607 06:27:54.811541 FromDcmtkBridge.cpp:141] Loading the external
DICOM dictionary "/usr/share/libdcmtk2/private.dic"
W0607 06:27:54.827478 OrthancInitialization.cpp:488] Registering JPEG
Lossless codecs
W0607 06:27:54.827613 OrthancInitialization.cpp:493] Registering JPEG
codecs
W0607 06:27:54.845340 OrthancInitialization.cpp:986] SQLite index
directory: "./OrthancStorage"
W0607 06:27:54.846042 OrthancInitialization.cpp:1056] Storage
directory: "./OrthancStorage"
W0607 06:27:54.848015 HttpClient.cpp:685] HTTPS will use the CA
certificates from this file: .
W0607 06:27:54.848730 ServerScheduler.cpp:134] The server scheduler
has started
W0607 06:27:54.849339 LuaContext.cpp:103] Lua says: Lua toolbox
installed
W0607 06:27:54.849526 ServerContext.cpp:181] Disk compression is
disabled
W0607 06:27:54.849597 ServerIndex.cpp:1402] No limit on the number of
stored patients
W0607 06:27:54.849676 ServerIndex.cpp:1419] No limit on the size of
the storage area
E0607 06:27:54.850612 DicomServer.cpp:306] cannot create network: TCP
Initialization Error: Address already in use
E0607 06:27:55.850235 main.cpp:1264] Uncaught exception, stopping
now: [The TCP port of the DICOM server is privileged or already in
use] (code 2004)
W0607 06:27:55.850906 main.cpp:1297] Orthanc has stopped
Could be TCP TIMEWAIT/socket SO_LINGER, maybe something a little more
obscure related to the virtual network. In any case, try without
manipulating the Orthanc process from within the container as explained
above (Orthanc should be PID1, it doesn't seem like a good idea to try
and restart it from within the container process namespace itself).
4.: I installed python-demjson but for this command got error message
again:
root@jodogne-orthanc1:/# jsonlint-py -Sf ./Configuration.json
bash: jsonlint-py: command not found
Did you install it on the host and are using it inside the container or
vice versa, by any chance? If not, then on a Debian-based system you
can list the contents of a package with `dpkg -L` to figure out the
command name and/or access to documentation. In any case, you shouldn't
need to run it from within the container.
Hope this helps,