ModuleNotFoundError: No module named 'pve_exporter'
See original GitHub issueGot this error when running the provided docker command. Is the dockerfile not importing the module correctly, or something a little more mysterious?
$ docker run -it --rm prompve/prometheus-pve-exporter --help
Traceback (most recent call last):
File "/usr/bin/pve_exporter", line 5, in <module>
from pve_exporter.cli import main
ModuleNotFoundError: No module named 'pve_exporter'
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
No module named 'prometheus-pve-exporter' - RoseIndia.Net
Hi, My Python program is throwing following error: ModuleNotFoundError: No module named 'prometheus-pve-exporter' How to remov.
Read more >prometheus-pve-exporter - PyPI
This is an exporter that exposes information gathered from Proxmox VE node for use by the Prometheus monitoring system. Installation. Note: Python 2...
Read more >[Question] What does module=default do? · Issue #108 - GitHub
hi Ive setup the exporter with default: user: prometheus@pve token_name: "prometheus" token_value: "token" ... when i curl without module
Read more >[Fixed] ModuleNotFoundError: No module named 'prometheus ...
Quick Fix: Python raises the ImportError: No module named 'prometheus-client' when it cannot find the library prometheus-client . The most frequent source ...
Read more >ImportError: No module named 'prometheus.client'
I'm running on ubuntu 18.10 and i got the same issue, and i have python2 install already. I was able to solved it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I released 2.0.1 which should fix the problem.
Uh, well. This is embarrassing. The
2.0.0
release on pypi.org is affected by the same packaging bug as well.