-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
standard_init_linux.go:211: exec user process caused "exec format error" #88
Comments
Hi @gabrielwhite, thank you for the detailed description. I have tried to recreate your environment, running it on arm/v7 with linuxserver/mariadb.
I will update the database migrations, and come back to ask you to verify that it works. Another thing, in your - PUBLIC_ENDPOINT=http://10.0.0.3:8088/ |
- Change max key-length of username to 128 - Fix minor syntax error
Hi again,
I found out that the Dockerfile was misconfigured, causing the cross-compilation to not work properly. It has been fixed in the newest commits. Could you please try again but using the |
Thanks for the quick fix. So I can now get the app up and running, but it's not showing photos and generating errors. I can create an account, and trigger a scan. The photos page is empty after running a scan. I set photos to /photos, per the Docker config. When I open the Albums page I get this error:
On the Albums page itself, this is shown
Here's the log:
Also, I commented out this in docker-compose, as it was generating other errors
Not sure how I should configure this? |
Hmm, it looks like mariadb is having some issues with a recursive query, I will look into that tomorrow. The PUBLIC_ENDPOINT env variable is very important for photoview to work. If it is generating other errors, please post them as well. It should be configured to the same as the url you type into the address bar in your browser to access photoview. |
Thanks! So I tried setting PUBLIC_ENDPOINT to these
And in both cases the logs were full of the same error (for what it's worth the docker host is 10.0.0.3 and my router is 10.0.0.1):
And I can't connect
As I said before if I'd left the line commented out I was able to get into the Photoview UI but with the errors I described above. Here's the docker-compose file again - I'm not sure whether my changed port mapping is affecting things?
|
Hmm.. It looks like
Do you think there exists a more up to date mariadb docker image for arm7? Regarding your last comment, the error you are getting doesn't seem to corelate with the PUBLIC_ENDPOINT variable. It looks like a problem with resolving the hostname |
I got it running, but now no photos are showing up. It seems to be scanning successfully (and the folders are showing up as albums), but the album thumbnails are blank and both the Photos page and within each album are empty. There seemed to be some issue with the configuration of this environment variable within the Docker environment. I changed this:
To this
I'd tried both host and bridge in the original configuration (db) you specified and neither worked. The (db) configuration resulted in these errors:
Here's my docker-compose
And here's the photoview log
The directories each have 4 JPG images. |
I was able to replicate it. The photos wasn't scanned because of a bug introduced in one of the most recently implemented features that hadn't been tested properly. I should be fixed in the commit bbff259. Please try to pull and rerun it:
|
Working! Thanks a million. |
No problem, I crushed some quite important bugs when debugging it. |
I have just tried to get this running on OMV5 (Debian Buster) / ARMv7 using the Docker compose.
The Docker PhotoView logs show this:
I can't access the server on the local network using it's IP (http://10.0.0.3:8088). I changed the port configuration in Docker below. The container itself keeps restarting.
I'm using the linuxserver/mariadb image because the stock mariadb image doesn't have an ARMv7 build.
Here's my docker-compose
I've tried the PUBLIC_ENDPOINT commented out completely, and on both ports 80 and 8088.
The mariadb logs don't show any errors
The text was updated successfully, but these errors were encountered: