bishopdynamics / kindle-touch-kiosk

Converting a Kindle Touch into a wall-mounted touchscreen kiosk for web-based interfaces like Home Assistant.
29 stars 2 forks source link

Docker errors (not sure how to even start debugging) #1

Open thephatmaster opened 8 months ago

thephatmaster commented 8 months ago

Hi there,

I loved the look of this project, and got the kindle bit done OK.

I'm running the docker container on a headless Pi4, but when I try to `docker compose up' I'm hit with a wall of errors. I'm not sure even where to start debugging.

Gamogamer commented 8 months ago

I have it working as of a few weeks ago. I got it set up with some help but here is how I did it as far as i remember.

I had help from a friend with this since i had never used docker before, or ubuntu server for that matter

While this works, the containers seem to break after one or more restarts and just crash on startup afterwards and I havent figured that issue out yet.

thephatmaster commented 8 months ago

It sounds like you're running a windows machine?

I've narrowed mine down to issues with running headless on linux (although it sounds like your virtual server is technically headless).

After chasing down most of the errors. Only ones relating to the x server or dbus remain:

vnc-kiosk-server-4-1 exited with code 1
vnc-kiosk-server-3-1  | [28:28:0209/094250.946771:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY
vnc-kiosk-server-3-1  | [28:28:0209/094250.946943:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.
vnc-kiosk-server-3-1  | [28:58:0209/094250.951198:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Gamogamer commented 8 months ago

Ah yea i get that exact error. And yes my server is Running windows server as host but docker is runnning in Linux. Which is headless. These Docker containers do some special stuff with the graphics, I believe it is set up as to use a virtual gpu or something like it.

Mine work again once I hit recreate, until i have to restart them, then they are broken. So I don't know if there is an automatic update that is breaking them or something else.

thephatmaster commented 8 months ago

So --force-recreate got me somewhere, but actually just more errors.

I now see a ton of stuff about variables not being set, Vulcan, opengl and all sorts.

Gamogamer commented 8 months ago

I haven't seen anything like that. I also don't use command line so I don't know the exact command portainer uses