sparklyballs

Are you using your Docker graylog or a physical machine? thanks, I'm definitely interested in this a hp n54l server that is primarily my tv-server.

I have a graylog server for all of my log entries for pfsense, unraid and a couple of other boxes, the entire disk usage is 343GB. but to mitigate that, it's also my tv-server and 335GB of that are tv-recordings, leaving 8GB split between system files of a debian wheezy server install and whatever logs are taking up from graylog. there are 3/4 million log entries according to the graylog stats page and the disk usage is in the low GB range. 3.4 gb in something like 6 weeks.

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.

Added desktop in a box with libreoffice, totaly experimental and things will probably break.

Bumped both kodi headless and koma to helix 14.2 (builds in progress on both)

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

hit it with a brick and put it in a sack.

that's already unraid'ed (is that a verb ?) to the point of user id being set.

don't know about this giftpd thingimy, but this looks doable. http://freedif.org/monsta-web-ftp-file-manager-in-php-ajax/

Added a few new containers.

i've forked smdions repo, (don't want ownership of it cos a lot of it is stuff i don't understand tbh) but i've played around with the htpcmanager docker. if i send you a pm can you check some bash scripting for me as i'm pretty new to it.

I'd be interested in how you get on with reverse proxying. I had a quick play with Apache but no luck as of yet. I was thinking this guy might be a good fit to take over smdions repo.

Awesome, i can still wear my cape with pride.

did you have a pre-existing docker for mylar ? sometimes if you still have the old xml left in /boot/config/plugins/dockerMan/templates-user the new settings don't take hold. also check in /boot/config/plugins/dockerMan/images for any mylar images zap em, reload info the docker page in the unraid webui and try re-adding.. if you don't have anything there in either folders then my docker hero powers are at their limit in terms of helping.

docker hero summit