Skip to content
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] Container not starting after update #81

Open
1 task done
pbeckcom opened this issue Jan 5, 2025 · 2 comments
Open
1 task done

[BUG] Container not starting after update #81

pbeckcom opened this issue Jan 5, 2025 · 2 comments

Comments

@pbeckcom
Copy link

pbeckcom commented Jan 5, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Contain fails to start after update to version 3abe9327-ls109. Re-pulling image did not resolve. was working prior to update
Screenshot 2025-01-05 111356
Screenshot 2025-01-05 111605

Expected Behavior

coitnainer should run

Steps To Reproduce

update image and see if it starts?

Environment

- OS:
- How docker service was installed: distro's pacakagemanager

CPU architecture

x86-64

Docker creation

used portainer, config worked prior to update, screenshots of config attached to description.

Container logs

2025-01-05T17:05:28.268177000Z [migrations] started
2025-01-05T17:05:28.268507000Z [migrations] no migrations found
2025-01-05T17:05:28.291617000Z ───────────────────────────────────────
2025-01-05T17:05:28.291802000Z       ██╗     ███████╗██╗ ██████╗
2025-01-05T17:05:28.291868000Z       ██║     ██╔════╝██║██╔═══██╗
2025-01-05T17:05:28.291935000Z       ██║     ███████╗██║██║   ██║
2025-01-05T17:05:28.292001000Z       ██║     ╚════██║██║██║   ██║
2025-01-05T17:05:28.292079000Z       ███████╗███████║██║╚██████╔╝
2025-01-05T17:05:28.292147000Z       ╚══════╝╚══════╝╚═╝ ╚═════╝
2025-01-05T17:05:28.292285000Z    Brought to you by linuxserver.io
2025-01-05T17:05:28.292354000Z ───────────────────────────────────────
2025-01-05T17:05:28.292490000Z To support LSIO projects visit:
2025-01-05T17:05:28.292559000Z https://www.linuxserver.io/donate/
2025-01-05T17:05:28.292739000Z ───────────────────────────────────────
2025-01-05T17:05:28.292811000Z GID/UID
2025-01-05T17:05:28.292875000Z ───────────────────────────────────────
2025-01-05T17:05:28.293910000Z User UID:    1000
2025-01-05T17:05:28.293965000Z User GID:    1000
2025-01-05T17:05:28.294019000Z ───────────────────────────────────────
2025-01-05T17:05:28.294243000Z Linuxserver.io version: 3abe9327-ls109
2025-01-05T17:05:28.294327000Z Build-date: 2025-01-05T11:52:38+00:00
2025-01-05T17:05:28.294387000Z ───────────────────────────────────────
2025-01-05T17:05:28.294442000Z     
2025-01-05T17:05:30.231591000Z [custom-init] No custom files found, skipping...
2025-01-05T17:05:30.356674000Z Traceback (most recent call last):
2025-01-05T17:05:30.356849000Z   File "/app/lazylibrarian/LazyLibrarian.py", line 25, in <module>
2025-01-05T17:05:30.356926000Z     from lazylibrarian import startup, webStart
2025-01-05T17:05:30.356997000Z   File "/app/lazylibrarian/lazylibrarian/startup.py", line 30, in <module>
2025-01-05T17:05:30.357069000Z     import cherrypy
2025-01-05T17:05:30.357139000Z ModuleNotFoundError: No module named 'cherrypy'
Copy link

github-actions bot commented Jan 5, 2025

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@j0nnymoe
Copy link
Member

j0nnymoe commented Jan 5, 2025

Don't use portainer to deploy our containers, you're probably hitting their "feature" https://info.linuxserver.io/issues/2023-05-22-portainer/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Issues
Development

No branches or pull requests

2 participants