Closed greedyro closed 6 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Try using a local folder on your VM rather than a remote mount.
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.
@j0nnymoe Same error message on my end, not using a mount
---
version: "2.1"
services:
heimdall:
image: lscr.io/linuxserver/heimdall:latest
container_name: heimdall
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/Utc
volumes:
- ./config:/config
network_mode: bridge
ports:
- 8082:80
restart: unless-stopped
I seem to have figured out the issue, the container needs internet access to pull something from github??? And it's spamming the log files with the error
Because it pulls down the app list for any updates.
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.
I have the same error log spam. But my container has internet access and i can ping github.com without problems.
For me it looks like there is an issue with the permission. The config folder is owned by abc? The containers start with the message:
Setting resolver to 127.0.0.11
Setting worker_processes to 4
generating self-signed keys in /config/keys, you can replace these with your own keys if required
New container detected, installing Heimdall
**** Permissions could not be set. This is probably because your volume mounts are remote or read-only. ****
**** The app may not work properly and we will not provide support for it. ****
Creating app key. This may take a while on slower systems
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.
I've just spun the container up with the same docker compose used above, on a Debian netinst system with local storage and have not been able to replicate the issue.
Happy to go into this further, but it seems as if there could be an issue with the system configurations here leading to the issues posted.
Closing for now.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
Instead of heimdall apearing in the broser i get: "504 Gateway Time-out nginx", and in docker logs i get a PHP fatal error
Expected Behavior
No response
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs