-
Notifications
You must be signed in to change notification settings - Fork 0
/
HOWTORUN
45 lines (38 loc) · 2.18 KB
/
HOWTORUN
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
#
# PRELIMINARIES -- on the "server"
#
# Build the container and then "run --name pftel " it.
# Depending on your purpose, choose either the Quick 'n dirty run --name pftel
# or, while developing, choose the run --name pftel with support for source debugging.
#
# Build (for fish shell syntax!)
set UID (id -u)
docker build --build-arg UID=$UID -t local/pftel .
# Quick 'n dirty run -- this is most likely what you'll mostly do.
# Obviously change port mappings if needed (and in the Dockerfile)
# Port 4005 is the actual pftel server, and port 22223 is the xinetd listener
# THIS STARTS IN INTERACTIVE MODE
docker run --name pftel --rm -it \
-p 22223:22223 \
-v /home/dicom:/home/dicom \
local/pftel /start-reload.sh
# For daemon, or background mode:
docker run --name pftel --rm -it -d \
-p 22223:22223 \
-v /home/dicom:/home/dicom \
local/pftel /start-reload.sh
# Quick 'n dirty run -- with volume mapping suitable for FNNDSC.
# Obviously change port mappings if needed (and in the Dockerfile)
# Here the -p 10502 mapping demonstrates how to map some external port
# on the host that might be receiving DICOM data to the internal listener.
docker run --name pftel --rm -it -d \
-p 22223:22223 \
-v /home/dicom:/home/dicom \
-v /neuro/users/chris/PACS:/neuro/users/chris/PACS \
local/pftel /start-reload.sh
# Run with support for source debugging
docker run --name pftel --rm -it \
-p 22223:22223 \
-v /home/dicom:/home/dicom \
-v $PWD/pftel:/app:ro \
local/pftel /start-reload.sh