{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/3300b8c6beae4cf9815d6c57672391c3\" frameborder=\"0\" width=\"1968\" height=\"1476\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1476,"width":1968,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1476,"thumbnail_width":1968,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/3300b8c6beae4cf9815d6c57672391c3-00001.gif","duration":96.604314532,"title":"Weird Behavior with Dev Containers and Initialized Command","description":"In this video, I discuss a strange behavior I'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'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."}