Jump to content

semtex41

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

3 Neutral

About semtex41

  • Rank
    Member

Recent Profile Visitors

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

  1. I will also add I was able to get docker-compose installed with the following: pip3 install docker-compose But I have no idea how unraid stores these nor if it will persist between reboots. Also, I still cant seem to uninstall python-2.7.17-x86_64-2.txz from within the Nerd Pack.
  2. On mine, its not letting me uninstall python2, and pip install docker-compose errors out on the same spot: subprocess32 I dont have anything using python myself. Any suggestions how to uninstall python2? (besides just turning the toggle to OFF and hitting apply)
  3. You need setuptools Thank you. And done. Sensing the pattern, I searched for json after I saw the following: Traceback (most recent call last): File "/usr/bin/docker-compose", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib64/python3.8/site-packages/pkg_resources/__init__.py", line 3252, in <module> def _initialize_master_working_set(): File "/usr/lib64/python3.8/site-packages/pkg_resources/__init__.py", line 3235, in _call_aside f(*args, **kwargs) File "/usr/lib64/python3.8/site-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib64/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_master ws.require(__requires__) File "/usr/lib64/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib64/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'jsonschema<4,>=2.5.1' distribution was not found and is required by docker-compose No dice. Have any advice how I can determine these dependencies and root them out? Thank you again.
  4. Having trouble after I updated docker-compose. First it threw an error about needing python3, so i installed it next to 2.7. Now it is stating: Traceback (most recent call last): File "/usr/bin/docker-compose", line 6, in <module> from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' I did remove/reinstall without success. Not positive of my previous version but here is the package that is failing: docker-compose-1.25.4-x86_64-1cf.txz Any suggestions? Thank you!
  5. I will join in on having this issue. 6x Axiom 120gb SSD in btrfs raid10 Performance has never been great, but I was able to confirm that docker sab extracting and downloading to the cache pool destroys performance and causes the server to lag horribly. Netdata pops with the warning: I am curious if this is any way related to this other issue, which is being worked on for 6.8rc: Btw, kudos to johnnie.black reporting and hounding that one to resolution. For this one though, I will keep watching and maybe this can get some attention in the future.
  6. I am curious, what setting did you have set on DirectIO option, when you were having corruption issues?
  7. I am also having this same issue. Not sure when it started as I rarely restart unraid or the pihole container (pihole/pihole:latest btw). But for me, if I do restart unraid, the pihole docker stops with the "DNS resolution is currently unavailable" in the docker logs. This is with the "Autostart" set to On in the GUI, for the pihole container. Starting the failed pihole container does work though, and it stays working until I reboot.
  8. Ok, at the suggestion of @SteelzFinest i went back and reread the thread. This is day 5 of my deep dive and I have finally tracked down the combo to keep the container running. TL;DR: Unraid Template upgraded from 3.0 and was causing problems. Change template VARIABLE (Key 7) from: br0 to eth0 Add Container Variables: PUID=99 PGID=100 _________________________ Chief Complaint: After upgrading from Pihole 3.x to latest, the web service is inaccessible and the container stops without restarting. The container stays running for approx 90 seconds. Problem persist even after a fresh rebuild, not using the previous docker image or anything saved in a docker volume. Scope: unraid pihole container running DNS only. DHCP is handled by an asus router. Observed symptoms: - Permission issues from the container with the docker volume - Inside the container, br0 is missing. - expected behavior with same physical network config is drastically different with Pihole 4.x (latest). Specifically, the previous config would resolve same network hostnames, even though "Never forward non-FQDNs" and "Never forward reverse lookups for private IP ranges" were both check on the previous version. - web server not responding - container crashes and fails to restart Example crash log: Starting pihole-FTL (no-daemon) Starting crond Starting lighttpd [services.d] done. /opt/pihole/gravity.sh: line 637: /etc/pihole/list.preEventHorizon: No such file or directory Stopping pihole-FTL Starting pihole-FTL (no-daemon) Stopping pihole-FTL Starting pihole-FTL (no-daemon) /opt/pihole/gravity.sh: line 637: /etc/pihole/list.preEventHorizon: No such file or directory comm: /etc/pihole/list.preEventHorizon: No such file or directory Stopping pihole-FTL Starting pihole-FTL (no-daemon) Stopping pihole-FTL Starting pihole-FTL (no-daemon) comm: file 1 is not in sorted order comm: file 1 is not in sorted order Stopping pihole-FTL Starting pihole-FTL (no-daemon) Detailed Workaround: With the template interface set to br0, I managed to restart the webservice by entering the containers and running the following: docker exec -it pihole bash Then, changing the default resolver config away from the default of 127.0.0.11 by running the following: cd /etc \ && find ${BASIN_SPIDER_CONFIG_PATH} -type f -name "resolv.conf" | xargs -L1 bash -c 'sed "s/nameserver 127.0.0.11/nameserver 127.0.0.1/g" $1 > /tmp/.intermediate-file-2431; cp /tmp/.intermediate-file-2431 $1;' -- \ && cat /etc/resolv.conf Since the container doesn't have any editors and running sed by itself revealed a file lock of some variety, I scrapped the above together based on some stack exchange suggestions. The container now stayed alive long enough that I was able to dig into the networking issue. My unraid template was assigning br0, which I eventually found was missing from inside the container. Changing the template Key 7 (Container Variable: Interface) to eth0 revealed through testing that the need to rename the default resolver was no longer needed. But the container was still crashing. NOTE: The Network Type is still Custom: br0 for me. Adding the respective container variables to the template appears to have solved the trick. Add Container Variables: PUID=99 PGID=100 See attached screencap. If this works for anyone else, let me know and I will share it on github. - semtex
  9. +1 The NVMe use-case mentioned previously is very applicable. Mainly it is order of magnitude difference in performance that drives this feature request.
  10. No worries. I did re-upload my logs (editing the comment) into zipped folders with better clarification. I appreciate you looking at it regardless.
  11. Affirmative, that is the correct zip. The timestamp in the file name confirms it. Where did you see the older version listed?
  12. I do have one issue to report, going from 6.5.0 -> 6.5.2. While at first I thought the install was flawless, a while later I realized my 10gbe connection wasn't working. Digging in, it looked like unraid was not detecting my HP NC523SFP (cLOM8214 1/10GbE Controller) card. Note: The card was working perfectly as I used the connection to copy files just prior to the upgrade process. Everything except the 10 gig nic seemed to be working fine. Docker, the array, etc. After rebooting a few times and still not seeing the card, I downgraded back to 6.5.0 and rebooted again, without success. Next, I powered off the box, disconnected the psu cable, and discharged the power button. After reconnecting power, the machine fired up and now the card was detected. I performed the upgrade again without issue. And rebooted again just to be sure. Now I am a living edge case and find bugs organically all the time. So this could have been a hardware issue, but I am not sure. The only things that physically moved the power cord being disconnected/reconnected and the power button to turn the box on. I do have some the diagnostic export starting after I reverted back to 6.5.0, but unfortunately I didnt think about it prior. Thanks all. Signed, A Noob logs from 6.5.0 rollback.zip
  13. Fixed this today by switching the docker volumes to /mnt/cache/... instead of /mnt/user/..... I plan on researching/submitting a feature change to get this tribal knowledge worked out of the forms and into the OS/Docker Templates/Help somehow. But thanks again to the people who posted this solution earlier in the thread.
  14. Hello, First attempt as using unraid and honestly I am quite excited at the concept of passing through my dailydriver/gaming pc VM. I understand this may not have been the primary customer use case, but for me this is my ultimate goal as it gives me the level of control I need and would reduce my overall physical hardware footprint. Snapshots would be the icing on the cake. But for now, I am having issues with passing through my GPUs to the VM i created. While I have given the forum a decent search and will continue to do so, would it be possible to help me understand either the ETA towards compatibility or maybe help me out on what I am missing? Please help me help you take my money.