-
-
Notifications
You must be signed in to change notification settings - Fork 70
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] Not working #160
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
I got the same error, same conditions. |
Provide full logs, it would include our logo in ascii |
User GID: 0 ....+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++..+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++........+.....+....+.........+......+..+.......+......+.....+.......+.....+.............+.....+.+.....+....+.........+........+.......+..+......+..........+...+.........+.....+......+.......+.....+....+...+...+..+......+...............+.+.....+.+.....+....+.....+.+............+.................+..........+...........+.........+...+.+...............+............+.........+.....+.............+...............+......+......+...+...+.....+...+.+.....+...................+..+.......+...+.....+....+...+...+...............+...+..............+......+.+...+.....+...+............+...............+...+...+.+...+...............+..+.........+.......+.........+.........+..............+...+.........+.+.........+.....+.+..+.+.....+....+...+........+.......+...+.....+.........+...+.........+....+..+...+.+...+.....+..........+...+...+.....+......+.+........+.+...+...+..+...+.......+..+.+........+..........+.................+.......+............+...+...........+.+.....+...+.+.....................+...+..+....+..+..........+..+............+...+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
I also get this error after pulling the most recent image and making a new container. The docker compose setup has not changed at all, and has been working for the past year. -- [migrations] started [custom-init] No custom files found, skipping...
|
|
Just for testing purposes, changing that does not solve the issue. |
Did anyone find a solution ? Just updated to latest version, but same error. |
Post more information about your setup: host os / hardware / cpu |
What specific CPU please |
@schellenberg did you solve this issue ? |
Same issue, here is the log:
The
|
Updated to latest build... |
I'm having the same issue with v7.20.0-ls309 on my Synology NAS. I went back to v7.2.0-ls256 and it's working again. |
Thanks, did the same and it's running |
v7.21.0-ls311 seems to have fixed this, I was able to run the current Docker container release without a problem. Or maybe it was fixed in a prior version but I hadn't tried in a while. |
My last known working version is v7.3.0-ls262. Anything newer throws an error like I've seen here. |
Same problem here with latest image (7.23.0)
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
comment to keep open |
Having the same issue using latest version (pulled just now).
|
Not helpful just saying you have the same issue. I'm going to guess all your systems have something in common which is why it's not working. You need to provide details about your setup as with the hardware I've got access to, I can replicate on synology (expected, really old EOL kernel) but works fine on other platforms (tested on unraid). And just for context, the container does work fine, shown here: https://ci-tests.linuxserver.io/linuxserver/calibre/latest/index.html |
Logs gives this error, sorry new to linux, any more information you need using any commands, please let me know happy to provide more information.
|
Need docker run/compose you've used along with hardware information. |
compose file as per request. Updated my CPU and hardware info in edit section of my previous posts in this thread.
|
My server is 24.04 Ubuntu LTS, I may have been on 22.04 at the time of my first report. It's a hosted KVM VPS, intel E5 cpu iirc. |
I've seen a user here before have an issue with KVM as it doesn't report/pass through all the correct details of the CPU and kasm has issues starting. |
Is there an existing issue for this?
Current Behavior
getting gateway timeouts, not working, no ui
Expected Behavior
it works
Steps To Reproduce
using ubuntu 24.04, latest docker
Environment
CPU architecture
x86-64
Docker creation
the compose file in the docs with the appropiate volume mappings
Container logs
The text was updated successfully, but these errors were encountered: