The folder creation solved my 500 server error and after creating it the error changed to the 400 client error. I wish I could help you but I spent a lot of time trying to solve this without any luck. I decided to completely switch my Synology (DS220+) install to an error free Home Assistant OS in VM.
My supervisor is 2021.02.6 and core is 2021.02.1,when i update the supervisor to the latest version,most my addons can not start with the error
500 Server Error for http+docker://localhost/v1.39/containers/7bbbb4dc1da00613132455461df66f342b2f42cf9c5726296ffee063ebb9d021/start: Internal Server Error (“OCI runtime create failed: container_linux.go:345: starting container process caused “exec: “/dev/init”: stat /dev/init: no such file or directory”: unknown”)
I dont know where is the problem with,Docker or supervisor? when i change the version of supervisor to old one 2021.01.7,some addons works fine,but my NODERED addon is missing from addons store and can not reinstall.
I have this same error after updating supervisor but only on SSH addon:
400 Client Error for http+docker://localhost/v1.39/containers/3e32d7d1f6e0f4dbdcc1ecadc1711dcf4a234e282a24bccd1277e47051821139/start: Bad Request ("OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown")
Same here:
with core-2021.1.5 and supervisor-2021.02.6 after restart of zigbee2mqttassistant version: 0.3.157 I got the error 500 Server Error for http+docker://localhost/v1.39/containers/5a83e74198c986935d1680f52c331a4e40ba8b1afb26db9fa94444bcdcfb37e2/start: Internal Server Error ("OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown")
Any hints to downgrade the supervisor?
Downgrade supervisor doesn’t solve the issue. I downgraded supervisor back to 2021.02.1.
No succes, still the same error.
400 Client Error for http+docker://localhost/v1.39/containers/ef6334dff603f7404c98f6d349c5a2a55b334e8ca38d73835b3c7579def0a97c/start: Bad Request ("OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown")
Hi,
What i've done :
Fix : Unable to load the panel source: /api/hassio/app/entrypoint.js
=> add a /bin/bash terminal on Hassio_Cli container and i've run the command : ha core rebuild
Fix : RPC shutdown error 500
=> when you install and try to start rpc shutdown addon, the container created try to mount le /dev volume on host and it shouldn't.
edit/replace rpc shutdown container from portainer (not visible under DSM) and delete volume /dev on host /dev then click deploy and valide replace the existing one.
then restart hassio (never stop rpc container cause it will be created with the /dev volume)
tested on core-2021.2.2 and supervisor-2021.02.6
I’ve downgraded supervisor to 2021.1.5, but it was done in vain. When I start more or less any addon, it rewards me displaying the following error:
Internal Server Error ("OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown")
Any idea what I could do? What else could be downgraded in order to make it work? Also restoring a snapshot does not help. My complete system is currently not working and it is not good, because I e.g. need some light in the evenings.
I’m totally fed up with this update philosophy. Each time you need to be careful, because they want to get rid of Synology users and therefore breaking changes are always kept in the dark.
I feel your pain. I’ve started looking into the virtual machine options described above, on top of having already submitted requests to Synology to update the version of Docker used in DSM. I recommend you do the latter as well to prod them along.
i have updated to the last supervisor update on syno…and now i have tihs error:
Internal Server Error (“OCI runtime create failed: container_linux.go:345: starting container process caused “exec: “/dev/init”: stat /dev/init: no such file or directory”: unknown”)
Impossible to start addons mosquitto & duckDns.
Restore snapshot not work, reinstalled docker & Hassio same problems.
After update ESPHome addon, the errores started. I had the great idea of reboot Synology and now its impossible start any addons. Allways error:
Error (“OCI runtime create failed: container_linux.go:345: starting container process caused “exec: “/dev/init”: stat /dev/init: no such file or directory”: unknown”)