(HTTP code 409) conflict - conflict: unable to delete 1652338c2fe7 (cannot be forced) - image has dependent child images

Product support
1

Getting this odd error: Service is already running ‘motioneye sha256:821eb138a798a12355cb6abf9303869744bb27e658cc04b8234910abc585ba25’
24.12.19 21:16:18 (-0800) Error cleaning up sha256:1652338c2fe7f7286bd15317a7005322f0c69510011361e2dbb147ad59e3889e: (HTTP code 409) conflict - conflict: unable to delete 1652338c2fe7 (cannot be forced) - image has dependent child images - will ignore for 1 hour

Prevents motioneye from displaying any video feed. I tried following advice from this post: Strange message: "Error cleaning up: (HTTP code 409) conflict - conflict: unable to delete (cannot be forced)"

But when I run balena rmi 1652338c2fe7 in host os
I get Error response from daemon: conflict: unable to delete 1652338c2fe7 (cannot be forced) - image has dependent child image

Next post in that topic says to run this:
IMG="$(balena images | grep 'resin/\|balena/' | grep supervisor | grep none | awk '{print $3}')"
REPO="$(balena images | grep 'resin/\|balena/' | grep supervisor | grep none | awk '{print $1}')"
balena tag $IMG $REPO:foobar
balena rmi $REPO:foobar

But I get "balena tag" requires exactly 2 arguments. See 'balena tag --help'.

Usage: balena tag SOURCE_IMAGE[:TAG] TARGET_IMAGE[:TAG]

Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE

Trying to get this backup and running ASAP, so any advice or help would be much appreciated.

Thanks.

2

Hi, can you grant support access to the device so that we can take a closer look?

4

Hi @karaxuna, I’ve granted support access for a day, let me know if you need more time. Thanks for your help!

7

Hello, sorry but could you also share the device UUID with us? You can copy that directly from the device summary page.

9

Note that if the UUID of your device is shared publicly, it allows anyone to visit the device’s public URL (only if it is enabled). If you prefer we can send you an email to reply to with the UUID?

12

Yeah, would be good if you could send an email.

24

Hi
I was able to run the right commands and get rid of the additional container. So far the logs haven’t shown the error you were facing and I expect it to stay that way.

Please let us know if you run into any more issues

26

Hi,

Looks like it’s still not working. Won’t display a motioneye camera feed.

On start up:

Service is already running 'motioneye sha256:821eb138a798a12355cb6abf9303869744bb27e658cc04b8234910abc585ba25'

Also getting:

INFO: server started
Failed to open /dev/v4l/by-id/usb-045e_USB_camera-video-index0: No such file or directory

27

Hi there,

That startup message you pointed out should be benign. Additionally it looks like the path you are using to access the camera device may be incorrect (below find the /dev path that’s accessible in the container now):

root@1a21109:/dev/v4l/by-id# ls -lthr
total 0
lrwxrwxrwx 1 root root 12 Dec 31 18:07 usb-046d_081b_A2D88230-video-index0 -> ../../video0

Would you mind detailing a bit more about the timeline that led up to this container failing? Is this a new release, or a device that had been working and now all of a sudden is not?

Finally, we always recommend staying up-to-date on OS upgrades as this host OS is quite old and many bugs have been fixed since it was released. You can learn more about those upgrades here: https://www.balena.io/docs/reference/OS/updates/self-service/!

28

The USB error has gone away and there’s no errors anymore but the camera feed still doesn’t work. Very odd. Tried updating but that didn’t fix it.

The container was working until a few weeks ago, when it suddenly stopped displaying video.

Any suggestions?

29

It appears as though there are now two video devices available:

root@1a21109:/dev/v4l/by-id# ls -lthr
total 0
lrwxrwxrwx 1 root root 12 Dec 31 19:09 usb-046d_081b_A2D88230-video-index1 -> ../../video1
lrwxrwxrwx 1 root root 12 Dec 31 19:09 usb-046d_081b_A2D88230-video-index0 -> ../../video0

Have you tried connecting to both of those devices?

31

There’s only 1 camera plugged in, so I’m not sure why there’d be 2 devices.

32

Hi there, could you provide some info on the last working BalenaOS version? Also, a detailed timeline of changes and the camera service status would help. Cheers!