sparklyballs

what a great idea...

even worse with containers from docker hub that are for general use rather than unraid aware containers is that there is no concept of a user share etc... so the likelihood of a rm -rf on a whole folder tree is higher...

not in my case, because i don't do any copy or moves in those kinds of folders (media, etc). but i've seen it in other containers. one thing you absolutely have to bear in mind with pretty much most dockers is that they are root user, it's just not good in all kinds of ways to give a container that much access to /mnt/user

on sunday whilst testing a container (and sometimes to make it easier during testing, i pass through at /mnt/user level) i deleted the entire contents of /mnt/user/appdata because of a misplaced rm -rf in a firstrun file.

maybe, but I've never had such an issue, and have passed /mnt/user since day 1, literally. if an author messes up a script, and it deletes data, it would delete data in whatever got mapped, so it would still be a pretty big disaster, right? I've seen dozens of posts in the last week about this mapping issue, and ALL of them would not have been asked it they had passed /mnt/user to /mnt/user. maybe it is "dangerous", but actual use has not shown it to be problematic thus far. The current method of passing limited folders has shown to be very problematic. I'm not saying you're incorrect, just that the real world shows my method works great; so far *also, as a person that has not authored a docker personally, how bad must a script be to actually delete user data on mapped drives? is it really a likely possibility, or a very, very remote possibility? Seriously, not rhetorical, I honestly don't know. want me to write a container that will demonstrate it , lol

ugh, using /mnt or /mnt/user leaves you at the mercy of the docker author, they mess something up in a script and you can end up with all your permissions changed or even worse stuff getting deleted, one of the good things about dockers and mapping is that you can limit what folders a container has access and mitigate any potential dangers, passing through /mnt or /mnt/user undoes that.

as i have probably stated before i'm hopeless at writing things up, but just going on things i see getting asked a lot, should cover (in no particular order). linking between containers , ie between sab and sickbeard folder and port mapping where to put the image file where to put appdata. Moderator edit: with abject apologies to SparklyBalls, since his post was the first, I'm commandeering the bottom of it to start this feedback topic for the Docker FAQ. I decided to pull weight a bit, to keep the FAQ clean, and move all other commentary, relevant or not, to this thread, nothing deleted. The discussion is good, but this is a better place for it. It's also available for FAQ requests and suggestions.

manually create the container on the unraid box itself and you can stop/start it from the dashboard like any other container. only thing i found doing it like that (or at least the last time i did) is that you get an orphan image for the base build that isn't easily deletable because unraid thinks it's in use by other dockers that may use the same base image.

for me, i have a ubuntu 14.04 VM that i've installed docker in, following the instructions on the docker website. then i write a dockerfile (got enough now that a lot of it is copy paste, dependant on type) and build it on the VM. that's 1 way, if it's a tougher docker, i fire up a container with just bash and try to build from straight linux commands, then play them back to create the dockerfile once i've found what works.

i build my dockers in a VM running on my unraid server.

It doesn't like your chip identifiers, were these entered manually or found by detect ? In the latter case you might need a newer version of sensors-detect (it was mentioned in another thread but I don't have it at hand) i'll have another go when this round of preclears have completed. thanks for your help.

root@HP-UnRAID:/boot/config/plugins/dynamix.system.temp# sensors Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced sensors_init: Can't parse bus name root@HP-UnRAID:/boot/config/plugins/dynamix.system.temp# cat /etc/sensors.d/sensors.conf # sensors chip "jc42-i2c-0-18" label "temp1" "CPU Temp" chip "jc42-i2c-0-19" label "temp1" "MB Temp"

In the final release of unRAID 6 there is no perl package included. This needs be installed manually and is needed to make detect work. You can download the package from http://slackware.cs.utah.edu/pub/slackware/slackware64-14.1/slackware64/d/perl-5.18.1-x86_64-1.txz and save under /boot/extra Why ?? can i use a command line entry to install that (it's in my newly created /boot/extras folder) because i'm running a preclear at the moment. installpkg is what unRAID uses to install slackware packages in /boot/extra when it boots. ok, cool, similar to installplg from when i was running v5. installpkg was around before plugins. I think it is just normal slackware. slackware is a dark art, lol.

In the final release of unRAID 6 there is no perl package included. This needs be installed manually and is needed to make detect work. You can download the package from http://slackware.cs.utah.edu/pub/slackware/slackware64-14.1/slackware64/d/perl-5.18.1-x86_64-1.txz and save under /boot/extra Why ?? can i use a command line entry to install that (it's in my newly created /boot/extras folder) because i'm running a preclear at the moment. installpkg is what unRAID uses to install slackware packages in /boot/extra when it boots. ok, cool, similar to installplg from when i was running v5.

In the final release of unRAID 6 there is no perl package included. This needs be installed manually and is needed to make detect work. You can download the package from http://slackware.cs.utah.edu/pub/slackware/slackware64-14.1/slackware64/d/perl-5.18.1-x86_64-1.txz and save under /boot/extra Why ?? can i use a command line entry to install that (it's in my newly created /boot/extras folder) because i'm running a preclear at the moment.

does this work for HP N54 microserver , can anyone confirm ? (this being , system temps, oops) didn't have the perl package....

keep that size

Nobody likes blue balls

it doesn't address the issue of red/green colour blindness though.

i think bonieni said the current icons were 16x16 somewhere in this thread.

I remember doing transparent background colors with gifs years ago. Am I missing something? With tranparent color, I mean "no background color", this is definitely not possible in gif format, contrary to png format, but the latter one doesn't support animation. test http://graphicdesign.stackexchange.com/questions/39772/making-backgrounds-of-animated-gif-files-transparent

how about a "switch" for colour blindness sufferers that turns all the icons to purely character based ? What about other icons. Green Check Mark Yellow Exclamation RED Big X an "O" of any colour for no disk present type events

even if i can't add anything constructive in terms of design, i like that this is being thought about. it's very important as it's the "shop window" for new users.

how about a "switch" for colour blindness sufferers that turns all the icons to purely character based ?

sparkly ball icon set...... Why did I plant that seed in your mind? What was I thinking?! mouseovers with sound... "AH YEAH" for everything is good "DISCO INFERNO" for things are going wrong