sparklyballs

i'll link you to the github, it's not in dockerhub yet. https://github.com/sparklyballs/docker-containers it's the calibre-desk folder there.

i think it would be good to stay on stock phusion base, as regards to the dev team, i've not made any approaches.

http://mispdev.blogspot.co.uk/2014/04/x11vnc-avoiding-buffer-overflow-when.html

i took the tmm container apart and put it together into a more traditonal Dockerfile as i find that easier to work with personally. i've been trying a couple of things, first i went back to "stock" phusion-base and added in the utopic repos to install x11vnc and then took them out again to call everything else, it starts but i'm having issues with setup screen on calibre, not certain if i've cocked up something else, looking later at that. if that don't sail, i'll try and compile another x11vnc from a writeup dated last week sometime specifically to address ipv6 issues

i've built a container out of calibre, (mainly for testing), using yours as a base. the only thing is though, i don't like the desktop switching in openbox, do you know there is any way to force it to have only one so it doesn't switch ? EDIT: think i may have found it. http://openbox.org/wiki/Help:Configuration#Desktops

i just forked this , hope you don't mind. was going to try and pick it apart , use your compiled binaries and use it for single use containers at a later stage.

i may have "fixed" my issue too, i found the config file for building the node packages and took out the references to ipv6 it's not throwing up any errors so far, just having issues connecting to the server, but i had this before where i got the build commands in the wrong order.

how about explicitly disabling ipv6 in the container, is that possible ?

i'm not up on kernel stuff, but it does seem a likely candidate given we are both experiencing issues related to ipv6.

have to ask what the dependencies and configure was i guess ?

i can run the docker in my docker server VM and it works nicely and i can videochat to myself thus far, lol. soon as i try it on my unraid box and it spits out some random errors specific to the app which google says is ipv6 related.

i'm trying to get a video conferencing server in a docker, running and i'm hitting this ipv6 issue too.

Thanks, I'm sure you are right, but I feel I don't have sufficient experience to write one. As you can see in the Learning about Dockers section, I cheated! I just pointed to what others had written, which seems well written but doesn't completely answer the question. The LimeTech Docker Guide gives a brief intro to them, then shows you how to create them. Jon's User V6 Manual says why they are better, and describes many characteristics of them, but I still don't have a good clear and simple description. After a fair amount of reading, my sense is that a Docker Container is a pluggable layered sandbox, pre-configured, prefilled with sand and toys. Is that anywhere close? I have yet to see the word 'sandbox' used anywhere, in connection with Dockers. It's more than a layer, it's more than a sandbox, it's more than a combination plugin. It sounds a lot like a VM! But I know it isn't. But then again, I haven't used them yet, which is why I would prefer to hear from a Docker user. How would you define a Docker? I'd be the last person you'd want to write anything like that, lol. i use terms like thingimy and watchacallit a lot. I would say less on the tech aspect, something along the lines of an app in a box but with more tech aspect than that, lol. good luck.

Perhaps a brief blurb on what a docker actually is, in the docker section.

I've discovered something very very worrying about the urbackup container with btrfs tools, it's making ghost copies of the container which cannot be deleted, delete the container and image it gives you a warning about being unable to delete a snapshot. then reboot and there are ghost containers appearing on my dashboard that you can delete, but survive a reboot and are there again. i am going to message jonp about this, because i'm very concerned that it's doing things to the docker.img file that it really shouldn't be.

Basically until the databases can be saved outside of the container, then this is going to be unusable. if you don't update the container then settings will not be lost, but fairly quickly those databases will be in the gb size range, at some point they'll outgrow the size of the docker.img file and the app will crash, not good in a backup app.

It didn't work anyways, lol. But I did discover something, and i've not seen this with any other container and i've absolutely no idea why it happens. If i disable running the start server and then exec in to the container, it will start if i issue the command manually.

`configure' configures urbackup-server 1.4.8.1014 to adapt to many kinds of systems. Usage: ./configure [OPTION]... [VAR=VALUE]... To assign environment variables (e.g., CC, CFLAGS...), specify them as VAR=VALUE. See below for descriptions of some of the useful variables. Defaults for the options are specified in brackets. Configuration: -h, --help display this help and exit --help=short display options specific to this package --help=recursive display the short help of all the included packages -V, --version display version information and exit -q, --quiet, --silent do not print `checking ...' messages --cache-file=FILE cache test results in FILE [disabled] -C, --config-cache alias for `--cache-file=config.cache' -n, --no-create do not create output files --srcdir=DIR find the sources in DIR [configure dir or `..'] Installation directories: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [PREFIX] By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc. You can specify an installation prefix other than `/usr/local' using `--prefix', for instance `--prefix=$HOME'. For better control, use the options below. Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir=DIR program executables [EPREFIX/libexec] --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include] --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] --datadir=DIR read-only architecture-independent data [DATAROOTDIR] --infodir=DIR info documentation [DATAROOTDIR/info] --localedir=DIR locale-dependent data [DATAROOTDIR/locale] --mandir=DIR man documentation [DATAROOTDIR/man] --docdir=DIR documentation root [DATAROOTDIR/doc/urbackup-server] --htmldir=DIR html documentation [DOCDIR] --dvidir=DIR dvi documentation [DOCDIR] --pdfdir=DIR pdf documentation [DOCDIR] --psdir=DIR ps documentation [DOCDIR] Program names: --program-prefix=PREFIX prepend PREFIX to installed program names --program-suffix=SUFFIX append SUFFIX to installed program names --program-transform-name=PROGRAM run sed PROGRAM on installed program names System types: --build=BUILD configure for building on BUILD [guessed] --host=HOST cross-compile to build programs to run on HOST [bUILD] Optional Features: --disable-option-checking ignore unrecognized --enable/--with options --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --enable-silent-rules less verbose build output (undo: "make V=1") --disable-silent-rules verbose build output (undo: "make V=0") --enable-install_initd Enables installing of supplied init.d file into /etc/init.d --enable-packaging Will be installed for packaging. --disable-fortify Disable GCC/runtime fortification --enable-dependency-tracking do not reject slow dependency extractors --disable-dependency-tracking speeds up one-time build Optional Packages: --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --without-mail Disables server mailing features. Use this to remove the dependency on libcurl. --without-crypto Disables cryptography functions. Internet mode will not be available. Use this to remove the dependency on libcrypto++. --with-mountvhd Enable mounting of VHD files via fuse. Some influential environment variables: CXX C++ compiler command CXXFLAGS C++ compiler flags LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a nonstandard directory <lib dir> LIBS libraries to pass to the linker, e.g. -l<library> CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if you have headers in a nonstandard directory <include dir> CC C compiler command CFLAGS C compiler flags CPP C preprocessor Use these variables to override the choices made by `configure' or to help it to find libraries and programs with nonstandard names/locations. Report bugs to <[email protected]>. that's the configure options in the source code. looking at that, perhaps using the option --without-crypto might solve the issue, but then would disable the internet backup feature. it's fairly easy to build though.

I've rebuilt the whole thing again, if you build it from git you can change two variables to select folders for the databases and the dcm4chee files and with the variables i've used everything gets changed automatically. There's also a placeholder output volume called IMAGES in the root. I've also swapped out runit in favour of supervisor, both the database and dcm4chee run as nobody:users, if you take out this section here from the Dockerfile, you take out the unraid specifics and it becomes portable. # Fix a Debianism of the nobody's uid being 65534 RUN usermod -u 99 nobody && \ usermod -g 100 nobody && \ (just remember to add the RUN back in to the next command in the Dockerfile) git here. https://github.com/sparklyballs/pacs

The databases and the dcm4chee setup are made inside the image when built on dockerhub. When you run the container locally for the first time, they are copied to local storage. So if anything ever cocks up (or you just want to test it out on dummy data etc...) , if you delete the contents of the database and dicom folders on local storage and restart the container, it takes you back to a virgin install again.

I've put it into my beta repo, it really needs someone who knows this software to take a look at it, I wouldn't even know where to begin with running it. The default password is admin/admin the webui link in dockerman takes you to the "records interface" there is another interface which seems to be for settings etc... at /jmx-console

it still needs modification of the startup scripts in that other docker and a script to check for existing databases and if they don't exist, create them.

Had a play with the preexisting docker and thus far I have this. FROM phusion/baseimage:0.9.16 ENV DEBIAN_FRONTEND noninteractive # Set correct environment variables ENV HOME /root ENV TERM xterm # Use baseimage-docker's init system CMD ["/sbin/my_init"] # output volumes VOLUME /DICOM /DATABASE # expose ports EXPOSE 8080 11112 # Add local files ADD src/ /root/ # Fix a Debianism of the nobody's uid being 65534 RUN usermod -u 99 nobody && \ usermod -g 100 nobody && \ # set temporary installation folder DCM4CHEE_TEMP=/root/temp-setup/dcm4chee && \ mkdir -p $DCM4CHEE_TEMP && \ # install dependencies apt-get update && \ apt-get install -y wget unzip mysql-server openjdk-6-jdk && \ # fetch, unzip and install required packages cd $DCM4CHEE_TEMP && \ wget --directory-prefix=/root http://sourceforge.net/projects/dcm4che/files/dcm4chee/2.17.1/dcm4chee-2.17.1-mysql.zip && \ unzip -q /root/dcm4chee-2.17.1-mysql.zip && \ DCM_DIR=$DCM4CHEE_TEMP/dcm4chee-2.17.1-mysql && \ wget --directory-prefix=/root http://colocrossing.dl.sourceforge.net/project/jboss/JBoss/JBoss-4.2.3.GA/jboss-4.2.3.GA-jdk6.zip && \ unzip -q /root/jboss-4.2.3.GA-jdk6.zip && \ JBOSS_DIR=$DCM4CHEE_TEMP/jboss-4.2.3.GA && \ wget --directory-prefix=/root http://sourceforge.net/projects/dcm4che/files/dcm4chee-arr/3.0.11/dcm4chee-arr-3.0.11-mysql.zip && \ unzip -q /root/dcm4chee-arr-3.0.11-mysql.zip && \ ARR_DIR=$DCM4CHEE_TEMP/dcm4chee-arr-3.0.11-mysql && \ rm -rf /root/*.zip && \ $DCM_DIR/bin/install_jboss.sh jboss-4.2.3.GA > /dev/null && \ $DCM_DIR/bin/install_arr.sh dcm4chee-arr-3.0.11-mysql > /dev/null && \ # Patch the JPEGImageEncoder issue for the WADO service sed -e "s/value=\"com.sun.media.imageioimpl.plugins.jpeg.CLibJPEGImageWriter\"/value=\"com.sun.image.codec.jpeg.JPEGImageEncoder\"/g" < $DCM_DIR/server/default/conf/xmdesc/dcm4chee-wado-xmbean.xml > dcm4chee-wado-xmbean.xml && \ mv dcm4chee-wado-xmbean.xml $DCM_DIR/server/default/conf/xmdesc/dcm4chee-wado-xmbean.xml && \ # Update environment variables echo "\ JAVA_HOME=/usr/lib/jvm/java-6-openjdk-amd64\n\ PATH=\"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin\"\n\ " > /etc/environment && \ # clean up apt etc.... apt-get clean && \ rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

I see, a little digging around and I found a pre-existing docker for this, which could be adapted to fit unraid. https://github.com/dpatriarche/docker-dcm4chee I forked it and ran a build in my docker vm i use for test building. I got some kind of web interface for settings etc... and then some records interface.

does this thing need hardware input for the images ? i found this setup guide that's a little dated but claims to get things up and running in minutes.. http://cdmedicpacsweb.sourceforge.net/CDMEDIC_PACS_WEB.html