Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About BoxOfSnoo

  • Rank
  1. Just my first name. It works though. the trick was echo -n password And not echo ‘password’
  2. I wa about to say “no that’s not it” but I went and looked at my config and yup, that’s exactly it. Since I copied and pasted, the /mnt/cache path was entered when I was typically using the /mnt/user/appdata path in all of my previous tests. Interesting, and fantastic detective work!
  3. Yes, I'm on rc7. I built mine using "Add Container" and plugging in the values as recommended above.
  4. I actually forget exactly how I found it - I know I tried to get the most current one from Microsoft's repo. I think I may have started with the Dockerhub template and changed the repository source.
  5. DUDE, it works! What's the difference from what I was doing? I made it all manually using your settings, maybe that was it. I also noted that the path has a trailing / - which I don't think I had before? Not sure if that makes any difference. The only thing it doesn't do is grab the icon, not sure why
  6. Be informed, though, that the problem I am encountering is exactly do do with persistence. Once you configure volumes, expect the container to crash. I haven figured out a great solution yet.
  7. Found some help on discord. The problem is the md5 for an empty password - doesn't work. Try "5f4dcc3b5aa765d61d8327deb882cf99" for the password "password". If you want to generate a new one, go to a console and type something like: echo -n br1lli@ntPa$sw0rd | md5sum
  8. I am getting this same thing, just installed and run from Community Applications.
  9. This doesn’t work for me, I am still using the unRAID web UI though.
  10. Ok thanks, I will try the specific version... How are you managing this through unRAID? Are you doing this through the command line and this docker-compose file?
  11. Anyone still working on running MS-SQL? I use it for development and I'd really hate to have to load the Windows version in a VM. I tried the memory and ulimit settings above, and it crashes. To be clear, it crashes when I map /var/opt/mssql to anything. I had this trouble on a Mac host before I started running unRAID, but I used a named volume instead. I can't see that that is a good idea for unRAID though - since it is all going to fill up the docker image? Is that my only option? This works: mssql:/var/opt/mssql This crashes the server: /mnt/user/appdata/mssql:/var/opt/mssql Also these crash the server: /mnt/user/appdata/mssql/data:/var/opt/mssql/data /mnt/user/appdata/mssql/log:/var/opt/mssql/log /mnt/user/appdata/mssql/backups:/var/opt/mssql/backups
  12. I'm not sure about the rest. I haven't seen those options. Do you need to have cheats on for those options? Also no idea about #2. Resource pack, maybe? I would try changing the server.properties to point at the other level that was initially installed and see if it all works correctly.
  13. Are you able to map the volumes to appdata? Whenever I do that it crashes. The only way I could get it to run was by using a named volume instead of a host path. Was it the ulimit and stack parameter that made it work?
  14. It should be: [ { "permission": "operator","xuid": "2533274801027666" } ]
  15. Probably some malformed json. Let's see your file?