shawly / docker-nut

Docker container for https://github.com/blawar/NUT. "latest" & "v3" tags use stable release v3.3. "edge" tag uses latest master source code.
GNU General Public License v3.0
63 stars 8 forks source link

Found files in the titles folder #2

Closed Pesoen closed 2 years ago

Pesoen commented 2 years ago

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] I would like a way to debug if it works correctly on the NUT end, as i can connect to my nut server just fine, but it does not show any of the three nsp files i have in there, all of which work just fine if i load up the nut server on my windows machine.

Describe the solution you'd like A clear and concise description of what you want to happen. a flag you can enable so it will list files in the titles folder that is found, can be some output of NUT or just a check of the files to check it sees the folder correctly.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. nothing really, other than trying different folders, since the current way is that the folder is actually hosted on my NAS, and is mapped as a local folder so all things should just see it as a folder, not some mysterious black hole.

Additional context Add any other context or screenshots about the feature request here. nothing really. i think i asked for what i wanted without too many spelling mistakes :P

Pesoen commented 2 years ago

got it working, had typed the folder name wrong so it did not see the directory correctly.. would still be a great debugging feature though :)

shawly commented 2 years ago

The feature to connect to your container and look at files already comes with Docker (e.g. docker exec -it <container name or id> /bin/bash to start a shell to look through files), I don't see much benefit from adding something like this.

Pesoen commented 2 years ago

The feature to connect to your container and look at files already comes with Docker (e.g. docker exec -it <container name or id> /bin/bash to start a shell to look through files), I don't see much benefit from adding something like this.

i did not know this. i am still rather new to docker, so thanks for telling me.

shawly commented 2 years ago

No worries, I might extend the troubleshooting section in the README.md and add some info about this. Permission and ownership problems are the most common issues people have with Docker. I've had quite a few issues opened in my other https://github.com/shawly/docker-ps3netsrv repo, so it might make sense to add the same troubleshooting steps for this image aswell.