Container doesn't restart automatically

Hello, We´re trying to run an image with Balena Engine but after restart, there’re some errors to start the container: `balena-engine run -d --name mycontainer -v certs:/certs:ro --network mynet -p 4430:443 --restart always myapp

balena-engine: Error response from daemon: Conflict. The container name “/mycontainer” is already in use by container “f9ea…cc9e”. You have to remove (or rename) that container to be able to reuse that name. balena engine start mycontainer Error response from daemon: driver failed programming external connectivity on endpoint mycontainer (0b145…bf79): (iptables failed: iptables --wait -t filter -A DOCKER ! -i br-ced36a917255 -o br-ced36a917255 -p tcp -d 172.17.0.4 --dport 443 -j ACCEPT: iptables: No chain/target/match by the name.```

                                             * It's a AXC F 2152 with Firmware 2020.6.1.
                                             * If we access as superuser, same issues.
                                             * The image run once, we've tried restarting the service with /etc/init.d/balena stop, /etc/init.d/balena start and balena-engine start myapp

Do you know which steps can we do? Regards, Samanta

Hi Samanta, I’ll take a look at this, Greetings, Jan

Hi, To the first error, the command balena-engine run is a combination of pull, create and start for the container. Name and ports can only be bind once. If the command has already been executed once, it will not work a second time with the same names and ports. Since the container is always created with --restart always, a command balena-engine start is not necessary to restart the container. The The error occurs already before. To the second error,iptables: No chain/target/match by the name,means that a kernel module for iptables is missing. Has anything been changed in the system? Either a module is missing from the kernel or a library is missing from the system. Can you give me the output from the container logfile: balena-engine logs Greetings, Jan