-
Notifications
You must be signed in to change notification settings - Fork 39
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
container not able to start. #14
Comments
I echo what ktoms71 says. I have installed in proxmox and it will not start. |
I would also like to add that the following error was logged: Job for pve-container@101.service failed because the control process exited with error code. |
same issue here, and it was working on this server with an older version of your script if it helps i run it with debugging log on and i get this:
i've also tried updating promox, disk space fine. Im able to mount container to. |
if you remove apt upgrade -y from install_tuya-convert.sh it worked for me
|
I'm not sure why it would not start the container. If you have updated Proxmox recently, make sure you reboot Proxmox if you are having problems. If you still receive this error, run |
Have the same problem. any progress on this? or use matbrewer396 link? |
Yes. After updating ProxMox it started right up. |
Idd it works :) only cant connect to samba for uploading the bin fil :( |
Hi, Im very much a proxmox and linux newbie. I ran the script to create the container. I can see in my promox dashboard that vm101 was created. When I go to start the container I receive the following error. Any thoughts? Again, I apologize if this is a user error.
Nov 16 11:39:04 nuc systemd[1]: Starting PVE LXC Container: 101...
Nov 16 11:39:04 nuc lxc-start[17655]: lxc-start: 101: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
The text was updated successfully, but these errors were encountered: