<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/3300b8c6beae4cf9815d6c57672391c3&quot; frameborder=&quot;0&quot; width=&quot;1968&quot; height=&quot;1476&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1476</height><width>1968</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1476</thumbnail_height><thumbnail_width>1968</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/3300b8c6beae4cf9815d6c57672391c3-00001.gif</thumbnail_url><duration>96.604314532</duration><title>Weird Behavior with Dev Containers and Initialized Command</title><description>In this video, I discuss a strange behavior I&apos;ve noticed with dev containers and the initialized command. According to the spec, the initialized command should run on the host machine before the container is built. However, I&apos;ve observed that the command is only executed when we build the container for the first time, not when we reopen an already built container. I demonstrate this behavior and discuss its implications. No specific action is requested from the viewers, but I encourage you to share your thoughts and experiences in the comments.</description></oembed>