October 19Oct 19 Hello all,I had a weird problem on my NAS, I found two of my containers had been stopped with no apparent reason. When trying to restart them from the GUI it failed with an error "403". I then proceeded to restart them from the command line and this time I got a more descriptive error message from the docker daemon: "endpoint with name <name of the container> already exists in network". Each one of the two containers belong to a separate network, one is in a custom "lan" network and the other is connected to br0.I tried to manually disconnect the containers from their respective networks but it did not help. Disabling/enabling docker somehow solved the issue.I never had this problem before. Because I recently upgraded to 7.3.2 I think maybe it is something related to this release?Has anybody encountered the same issue before ?
October 20Oct 20 Author Here is the diagnotics file.There's nothing in the docker log, the only suspicious activity is seen in syslog:Oct 16 23:10:43 Nas3 kernel: __vm_enough_memory: pid: 1960294, comm: VM Periodic Tas, bytes: 46371323994112 not enough memory for the allocation### [PREVIOUS LINE REPEATED 1 TIMES] ### Edited October 20Oct 20 by googleg
October 20Oct 20 The endpoint error and recovery after restarting Docker suggest that Docker retained an existing network attachment for a stopped container. These diagnostics do not establish what caused that state.The memory warning shows a rejected allocation of approximately 42 TiB. There is no OOM-killer event in the supplied logs. A container network interface becomes disabled four seconds later, so the timing could be relevant, but we cannot identify the container.Which two containers were affected, and when did they stop? Are they managed through Unraid’s Docker templates or Compose Manager Plus? Did this follow a container update or backup?If it happens again, please collect diagnostics before restarting Docker or disconnecting networks. Also run this for each affected container, replacing CONTAINER with its name:docker inspect --type container --format 'State={{json .State}} Networks={{json .NetworkSettings.Networks}}' CONTAINERThis will capture its exit state and network attachments while the problem is present.
October 20Oct 20 Author Ok thanks for the feedback, I will run the diagnotics and commands before restarting Docker if this happens again.The two containers that failed are named "selemium" and "chrome-rdk", and they are not managed through Docker Compose Manager. Edited October 20Oct 20 by googleg
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.