Mr. Anderson

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mr. Anderson's Achievements

Noob

Noob (1/14)

10

Reputation

  1. I very rarely use Community Applications to install containers on my server. Actually just today I finished making another container and getting it running on my server. If you can find a Docker container on Docker Hub, you can most likely get it running on unRAID with no issues. To setup a new container, just follow a few steps and you shouldn't have many issues. Read the official Docker container documentation very thoroughly. Seriously, I can't tell you how many times I've failed to get a container started because I missed a parameter, or how many containers I've skipped adding a volume to only to find out no config saved after a restart. Go to your Docker Tab in unRAID and click Add Container Leave the Template blank. unRAID will create a template when you get your container running Give it a name- not like Bob or Sally, but a name which is basically what the container is. Plex, LetsEncrypt, etc. In Repository, enter the Docker Hub repository along with the tag, eg. homeassistant/home-assistant:stable where stable is the tag. Docker Hub is good about telling you the Docker command to run the container, you just don't need the docker run portion in this field Network Type is where things can get tricky. Host shares the IP with the server. Bridge gives the container a unique IP address within the private network of Docker. Most of my containers use Bridge. If you want to get really technical you can create Docker networks. My Home Assistant container runs on a network I created that is on my smart home VLAN. If your container requires a PATH, and if you plan on saving data it will, click Add another Path, Port, Variable, Label or Device and in the dropdown select Port. Name is human readable only and I've played with a lot of different naming conventions, but I just stick to the container path without the leading slash, so config for example. Container Path is the path the container needs, so for my HA container, it's /config Host Path is the path on your unRAID server to store the data, so for my HA container, it's /mnt/cache/docker_stash/homeassistant/ and as you can see I've created a folder that only exists on my cache drive for Docker. This is unnecessary but I was using a small 15k drive when I created this and didn't have much space for anything other than my Docker container on the drive. This was just a workaround and I'll eventually move it all to another folder If your container requires a PORT, click Add another Path, Port, Variable, Label or Device and in the dropdown select Port Name is human readable only, but for the most part I just make it the port number. Sometimes I'll specify that it's for, like Web UI but that's rare Container Port is the port the container needs opened which will be in the container documentation Host Port is the port you want to direct this to on your unRAID server. If you have a container that needs port 80, this is where you would redirect to 81, 8080, etc. Connection Type is either TCP or UDP. Again the container documentation will tell you and if it doesn't, assume TCP. If it doesn't work, edit the container and try UDP. If you need more settings than you can access with the Add another Path, Port, Variable, Label or Device, then in the upper right you can toggle the switch that says Basic View and get into Advanced View. From here you can specify the Docker Hub URL, Icon URL and even the WebUI which for Home Assistant is http://[IP]:[PORT:8123]/lovelace. So you see you can do the IP, port and even a path all in here so you can easily access your UI from the main unRAID screen. Extra Parameters is where odd things go, such as on my Home Assistant I'm skipping my Pi-Hole container with --dns=1.1.1.1 to tell the container to use Cloudfare's DNS. As you can see, you have quite a bit of flexibility and power with unRAID. When I first got in and was learning about running Dockers on unRAID it sure seemed narrow minded just to limit myself to only the Community Applications and I wanted to figure out how to do it on my own. If there is already a Community Application that gets me there, I'll use it but I don't want to be limited to only that one place when there are so many containers. Also, the beauty of Docker is if 100 people make containers for something like Plex or Home Assistant, you can always switch your Repository if the one you are using isn't keeping current and just save your settings. As long as they aren't doing some weird stuff for their container, you shouldn't have to change any ports, paths, etc. and it should just work.
  2. Thank you! I started MongoDB expecting authentication originally. I was able to get my db users added and it's all working now.
  3. I'm having a hard time getting mine up and going. When I run the command to create the second user, I get a message saying "uncaught exception: Error: couldn't add user: command createUser requires authentication. I've shut down the MongoDB Docker and brought it back up, rebuilt it following the instructions about 3 times, but I always come to this same error.
  4. So sorry. Feel very dumb. I was in advanced view and thought it might show more options for Path, Port, Variable, Label or Device where I could set a custom. This answers all my unRAID container questions. Thank you so much and sorry for posting in the wrong place.
  5. I've seen that, just wondered if there was somewhere these were stored like they are displayed there so I can make changes. There are a couple parameters in the run command I cannot get set to look like MS documentation via the GUI, but don't know if it matters. For example the MS documentation shows the parameter -e 'ACCEPT_EULA=Y' but when I edit it through the GUI it shows like -e 'ACCEPT_EULA'='Y' with both the parameter and value wrapped in their own single quotes. Also MS documentation shows -d microsoft/mssql-server-linux:latest but I cannot get a -d parameter set via the GUI. I'm sure I'm missing something.
  6. They are asking me to share my Docker run command. Is there a place where these are stored in unRAID?
  7. If this thread is locked, then in my opinion there needs to be some general thread for a containers that don't already have their own thread. That's why I posted in this thread in the first place. It seemed to be a general thread, and since threads can't be created in this section, it seemed the only way to post an obscure issue for a barely used container.
  8. I think that might be what I have to do. I just wanted to try here just in case anyone was successfully running SQL on their unRAID server.
  9. Thanks. But I don't guess that will do me much good since I can't get the image to start, correct? Or is there a way to go to a container path with the container stopped?
  10. I'm trying to run a MS SQL docker on my server but am running into nothing but issues. Can't find an official thread on it, and in fact when I search 'sql' on the forum, there are 0 results. The docker is from https://hub.docker.com/r/microsoft/mssql-server and I have listed my log below. This is not my 1st docker to run on my server, but the others are well documented and supported here. This one is just giving me fits. It will stop within a few seconds of starting it. It is referencing a /var/opt path in the log, but I have no opt folder in /var and even if I create one, nothing gets populated. Can anyone tell me what I'm missing? Log: This program has encountered a fatal error and cannot continue running. The following diagnostic information is available: Reason: 0x00000003 Message: result Stacktrace: 000055f17a081962 000055f17a014427 Thread: 11 (application thread 0x1000) Instance Id: 241440d4-aad3-4cd2-bbaf-50e357d8ebef Crash Id: 69b82135-a8b6-487f-af1f-cd76529dd599 Build stamp: 1dc223c2c297541dfebf5ce3265c3e74bbe289d287259e15dd32bd77f11bc1bd Capturing core dump and information... No journal files were found. No journal files were found. Attempting to capture a dump with paldumper WARNING: Capture attempt failure detected Attempting to capture a filtered dump with paldumper WARNING: Attempt to capture dump failed. Reference /var/opt/mssql/log/core.sqlservr.7.temp/log/paldumper-debug.log for details Attempting to capture a dump with gdb WARNING: Unable to capture crash dump with GDB. You may need to allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or run as root.