Need some help here:
I got image and container installed and running, but where do I go on from here?
Docker GUI plugin now stable
-
- OMV 2.x
- nicjo814
-
-
I'm using this one: hub.docker.com/r/jinglemansweep/logitechmediaserver/
It's running fine and I can even use the 3'rd party Spotify plugin on it with my classic players. I had an install of LMS running on the server, which I removed, and now it's running in docker using very few resources. It's even faster now. Docker is really a very nice addition to the server.
@fafdk
Hi, can you share your Settings for the LMS Iám new to docker an LMS. Got it to work but the Music Scanning does not work. Permissions should be right.Thanks..
-
-
I have a question for the options in the run image window.
how can i take a parameter for a link in my local mysql database?
I don't understand the help from here:
http://forums.openmediavault.o…5/?postID=95997#post95997
and i think the question ist better here. -
Can somebody help me out here?
How to I launch my container?Here's the web service that I try to create:
-
I have a question for the options in the run image window.
how can i take a parameter for a link in my local mysql database?
I don't understand the help from here:
Plugins that are wanted - Part 5
and i think the question ist better here.To use the --link parameter in the plugin you need to run the latest testing version (0.2.17). In this version there is an "Extra arguments" field where you can enter any parameters not yet supported "natively" by the GUI. Here you colud link your containers together if you want to. However, when I read your original question in the thread you referred to it looks like you want to reach a "local" mysql installation from within your docker container. How this is accomplished probably depends on the container you are using...
-
Can somebody help me out here?
How to I launch my container?Here's the web service that I try to create:
From what I could see in your first post regarding this issue it looks like you haven't forwarded any host port to port 80 in the container. To accomplish this you need to stop and delete the container you already created. Then "re-create" the container and configure network settings in the "Networking" section of the plugin GUI. Here you should use "Bridged" mode and then forward some "unused" port on your server (maybe 9080 or something) to port 80 in the container. If done properly you should now be able to access your container via http://<your-host-ip>:9080
EDIT: Sorry for not responding earlier, I was away over the weekend without access to a proper internet connection...
-
So, I did that.
I got this error when I ran this commands in SSH: -
What is the default Network port that the Docker API listens on? i kinda changed it and want to set back the default again.
Thanks -
So, I did that.
I got this error when I ran this commands in SSH:All docker commands needs to run as root in the CLI. It looks like you ran that command as a regular user.
-
What is the default Network port that the Docker API listens on? i kinda changed it and want to set back the default again.
ThanksBy default docker doesn't use any network ports at all, instead it relies on communication via a Unix socket. I added a random (42005) port to the plugin to speed up communication/processing of information with the docker daemon. You can use any port you want as long as it's specified in the plugin GUI...
-
Gotcha. This docker is hard to use than VM or Virtualbox.
How come there is no step-by-step to use this Docker plugin in this forum?
I found only the basic guide. -
The plugin is still developing. Not many people working on it. A guide is pretty low on the priority list I guess. A lot of docker tutorials on the internet would probably help make the plugin make sense. Starting a couple of beginning docker books myself.
-
Personally I use this site quite a lot https://docs.docker.com and it covers almost everything regarding Docker.
-
This docker is hard to use than VM or Virtualbox.
True. You only need to run the commands "docker --help" and "docker run --help" to get an idea of how complex it is...
-
The container that I tried to run required MySQL to be installed.
I've installed it in Docker to run snipe-it, but no luck.Thanks for the help.
-
nicjo814
I finally fixed all the issues i had yesterday. There is one thing that i want to make sure though. Its about the correct IP in /etc/default/docker. ( addons can't be downloaded without modifying this).I have been using this based on this old docker thread
On this thread, kalle-del-haye had success using this (I changed mine to my IP)Both works for me.. Which of the following is more proper?
Also...
1. do we need to change something in watchdog's settings.xml, or leave it as it is?
2. After the add-ons has been downloaded, do we remove KODIADDONS=metadata.universal|service.watchdog in ENV, or leave it there too? cuz i thing its re-downloading everytime i restart the container or restarts OMV.Thanks
-
nicjo814
I finally fixed all the issues i had yesterday. There is one thing that i want to make sure though. Its about the correct IP in /etc/default/docker. ( addons can't be downloaded without modifying this).I have been using this based on this old docker thread
On this thread, kalle-del-haye had success using this (I changed mine to my IP)Both works for me.. Which of the following is more proper?
Also...
1. do we need to change something in watchdog's settings.xml, or leave it as it is?
2. After the add-ons has been downloaded, do we remove KODIADDONS=metadata.universal|service.watchdog in ENV, or leave it there too? cuz i thing its re-downloading everytime i restart the container or restarts OMV.Thanks
If you look at my config file it looks like this after the plugin has been installed and I've moved the location of my images/containers:
# Docker Upstart and SysVinit configuration file
# Customize location of Docker binary (especially for development testing).
#DOCKER="/usr/local/bin/docker"# Use DOCKER_OPTS to modify the daemon startup options.
#DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4"# If you need Docker to use an HTTP proxy, it can also be specified here.
#export http_proxy="http://127.0.0.1:3128/"# This is also a handy place to tweak where Docker's temporary files go.
#export TMPDIR="/mnt/bigdrive/docker-tmp"### Do not change these lines. They are added and updated by the OMV Docker GUI plugin.
OMVDOCKER_API="-H unix:///var/run/docker.sock -H tcp://127.0.0.1:42006"
OMVDOCKER_IMAGE_PATH="-g /var/lib/docker/openmediavault"
DOCKER_OPTS="$DOCKER_OPTS $OMVDOCKER_API $OMVDOCKER_IMAGE_PATH"
### Do not add any configuration below this line. It will be removed when the plugin is removedThe important part is that the first occurance of the DOCKER_OPTS variable must not contain any settings used in the last DOCKER_OPTS variable. In your case that would be DOCKER_OPTS="-H 127.0.0.1:4243 -H unix:///var/run/docker.sock" which would cause problems.
However DOCKER_OPTS="--dns 192.168.178.1" would be totally ok though.1. do we need to change something in watchdog's settings.xml, or leave it as it is?
If your sources.xml file is ok, you shouldn't have to do any changes to the Watchdog settings.xml file.2. After the add-ons has been downloaded, do we remove KODIADDONS=metadata.universal|service.watchdog in ENV, or leave it there too? cuz i thing its re-downloading everytime i restart the container or restarts OMV.
You can remove that parameter since it's just as you say. It will be downloaded every time the container starts otherwise. -
Know what would instantly give you 100's of pre-configured apps for this? If you supported unraids docker repositories .
Example: http://lime-technology.com/forum/index.php?topic=37958.0
Basically a "repository" is just a bunch of xml files. Each XML file has the config (volumes, ports, env vars, etc...) for a docker container.If OMV supported unraid repo's, it would be very easy for newbies to get started :). See the "Adding Template repositories" section here: http://lime-technology.com/docker-guide/ Many of the repo's on are github (ie opensource) so I wouldn't think this would violate any type of licensing if you use their opensource configs.
-
People using this plugin please do not upgrade to version 1.9 of docker-engine, everything will stop working if you restart the daemon or reboot
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!