Plugin installation after Upgrade not working anymore #10994

Closed
opened 2025-12-29 21:38:55 +01:00 by adam · 2 comments
Owner

Originally created by @basdscho23 on GitHub (Apr 7, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.1.7 v4.2.2

Python Version

3.12

Steps to Reproduce

Upgrade Netbox from v4.2.2. to an higher version and try to install any Plugin via pip

Expected Behavior

We have several Netbox instances running via docker which are all running in version v4.1.7.
In addition to the live, dev and test, I also have a local netbox running in my wsl, which I use for the development of our plugin.
The plugin and the local upgrade work up to version v4.2.2 without any problems.
As soon as I download the netbox image from Dockerhub with the larger v4.2.2, the plugin can no longer be installed because there is no pip in the venv. In other words, ‘pip install ’ no longer works. The plugin is specified in the config file.

Observed Behavior

We have several Netbox instances running via docker which are all running in version v4.1.7.
In addition to the live, dev and test, I also have a local netbox running in my wsl, which I use for the development of our plugin.
The plugin and the local upgrade work up to version v4.2.2 without any problems.
As soon as I download the netbox image from Dockerhub with the larger v4.2.2, the plugin can no longer be installed because there is no pip in the venv. In other words, ‘pip install ’ no longer works. The plugin is specified in the config file.
The problem also occurs when I execute the following command:
apt update && apt install pip -y
cd /opt/development/plugin # Plugin Directory mount point
pip install -e. --break-system-packages

Netbox then says that the plugin was successfully installed on the database, but even after migration of the plugin it cannot be found:
"django.core.exceptions.ImproperlyConfigured: Unable to import plugin netbox_it_service: Module not found. Check that the plugin module has been installed within the correct Python environment."

Originally created by @basdscho23 on GitHub (Apr 7, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.1.7 v4.2.2 ### Python Version 3.12 ### Steps to Reproduce Upgrade Netbox from v4.2.2. to an higher version and try to install any Plugin via pip ### Expected Behavior We have several Netbox instances running via docker which are all running in version v4.1.7. In addition to the live, dev and test, I also have a local netbox running in my wsl, which I use for the development of our plugin. The plugin and the local upgrade work up to version v4.2.2 without any problems. As soon as I download the netbox image from Dockerhub with the larger v4.2.2, the plugin can no longer be installed because there is no pip in the venv. In other words, ‘pip install <plugin>’ no longer works. The plugin is specified in the config file. ### Observed Behavior We have several Netbox instances running via docker which are all running in version v4.1.7. In addition to the live, dev and test, I also have a local netbox running in my wsl, which I use for the development of our plugin. The plugin and the local upgrade work up to version v4.2.2 without any problems. As soon as I download the netbox image from Dockerhub with the larger v4.2.2, the plugin can no longer be installed because there is no pip in the venv. In other words, ‘pip install <plugin>’ no longer works. The plugin is specified in the config file. The problem also occurs when I execute the following command: apt update && apt install pip -y cd /opt/development/plugin # Plugin Directory mount point pip install -e. --break-system-packages Netbox then says that the plugin was successfully installed on the database, but even after migration of the plugin it cannot be found: "django.core.exceptions.ImproperlyConfigured: Unable to import plugin netbox_it_service: Module not found. Check that the plugin module has been installed within the correct Python environment."
adam added the type: bug label 2025-12-29 21:38:55 +01:00
adam closed this issue 2025-12-29 21:38:56 +01:00
Author
Owner

@squintfox commented on GitHub (Apr 7, 2025):

@basdscho23 This isn't a NetBox problem. netbox-docker moved from pip to uv in the latest release: https://github.com/netbox-community/netbox-docker/releases/tag/3.2.0

The plugin install instructions are updated as well: https://github.com/netbox-community/netbox-docker/wiki/Using-Netbox-Plugins

@squintfox commented on GitHub (Apr 7, 2025): @basdscho23 This isn't a NetBox problem. netbox-docker moved from pip to uv in the latest release: https://github.com/netbox-community/netbox-docker/releases/tag/3.2.0 The plugin install instructions are updated as well: https://github.com/netbox-community/netbox-docker/wiki/Using-Netbox-Plugins
Author
Owner

@bctiemann commented on GitHub (Apr 7, 2025):

Closing as per above comment.

@bctiemann commented on GitHub (Apr 7, 2025): Closing as per above comment.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10994