-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] apparently breaking changes with v4.0.0-ls195 #54
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Getting exactly the same errors here, which has nerfed our test netbox container |
We'll have to take a look at the breaking changes in v4 and get the image updated |
Please test the PR image from #55 once it has completed building (it'll post the image tag as a comment in the PR). |
Thanks for the speedy fix, can confirm that the image in the PR works - at least as far as successfully starting up and logging in. Will now start delving into it on my test container and see what's new. |
Is there an existing issue for this?
Current Behavior
I upgraded from v3.7.8-ls194 to v4.0.0-ls195. Netbox throws an error:
s6-rc: warning: unable to start service init-netbox-config: command exited 1
Expected Behavior
Netbox should start
Steps To Reproduce
Not sure what to say, upgraded from v3.7.8-ls194 to v4.0.0-ls195.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: