<transcript><audio_63>inject a Seeker directly into a Docker service and this can either be done at runtime or it can be done anytime after by editing and and restarting the service uh each secret the secret is exposed to each task within that uh</transcript><transcript><audio_64>within that service via a default Run secets temp FS volume importantly this is in memory nothing is saved to the dis on these hostes uh but it's exposed to the container in a way that those secrets are now readable in a plain text file</transcript><transcript><audio_65>uh authorization you can within Docker data center you can tag secrets to a specific service so you can say only this service is allowed to see the secret and that means that no other service on the on the uh on the cluster can just grab those secrets so while the</transcript><transcript><audio_66>the the file itself is exposed in plain text the secret is encrypted uh and it's fully in memory so again only accessible to that small portion of container that's allowed to see it also with Docker data center admins can authorize via our act Ro based Access Control</transcript><transcript><audio_67>mechanism which users and teams have access to that secret uh and this works via the same Access Control label based mechanism that's used across other parts of the product using the goo you can also quickly rotate and update Secrets uh with to all containers in a service</transcript><transcript><audio_68>just by editing a service and starting and changing the secret or replacing the secret uh you can also audit request for that secret so using the CIS log feature built into UCP where you send out all of your logging data to something like an elk stack you can figure out which users</transcript> inject a Seeker directly into a Docker service and this can either be done at runtime or it can be done anytime after by editing and and restarting the service uh each secret the secret is exposed to each task within that uh within that service via a default Run secets temp FS volume importantly this is in memory nothing is saved to the dis on these hostes uh but it's exposed to the container in a way that those secrets are now readable in a plain text file uh authorization you can within Docker data center you can tag secrets to a specific service so you can say only this service is allowed to see the secret and that means that no other service on the on the uh on the cluster can just grab those secrets so while the the the file itself is exposed in plain text the secret is encrypted uh and it's fully in memory so again only accessible to that small portion of container that's allowed to see it also with Docker data center admins can authorize via our act Ro based Access Control mechanism which users and teams have access to that secret uh and this works via the same Access Control label based mechanism that's used across other parts of the product using the goo you can also quickly rotate and update Secrets uh with to all containers in a service just by editing a service and starting and changing the secret or replacing the secret uh you can also audit request for that secret so using the CIS log feature built into UCP where you send out all of your logging data to something like an elk stack you can figure out which users
{"source": "grass-yt-cc-by.180RC4tlwIQ|shard_10008_13|create_multimodal_data.extract_yt_and_generate_transcripts.57|shard_10008|create_multimodal_data.generate_captions.57|shard_10008|create_multimodal_data.generate_captions.57", "params": {"id": "180RC4tlwIQ", "channel_id": "UC76AVf2JkrwjxNKMuPpscHQ", "duration": 3452, "view_count": 1271, "age_limit": 0, "chapters": [{"start_time": 0, "end_time": 99.0, "title": "<Untitled Chapter 1>"}, {"start_time": 99.0, "title": "Docker at the center of enterprise IT transformation", "end_time": 212.0}, {"start_time": 212.0, "title": "Docker Datacenter Integrated Platform", "end_time": 341.0}, {"start_time": 341.0, "title": "Docker Datacenter CaaS Overview", "end_time": 432.0}, {"start_time": 432.0, "title": "What's New in Docker Datacenter on Docker 1.13", "end_time": 628.0}, {"start_time": 628.0, "title": "The Key Components of Container Security", "end_time": 709.0}, {"start_time": 709.0, "title": "Integrated Secrets Management", "end_time": 858.0}, {"start_time": 858.0, "title": "Safer Apps with Docker Security Scanning", "end_time": 976.0}, {"start_time": 976.0, "title": "Improved Access Control", "end_time": 1050.0}, {"start_time": 1050.0, "title": "Compose for Services", "end_time": 1114.0}, {"start_time": 1114.0, "title": "Image Content Cache", "end_time": 1240.0}, {"start_time": 1240.0, "title": "Built in HTTP Routing Mesh (Now GA!)", "end_time": 1374.0}, {"start_time": 1374.0, "title": "Webhooks for Registry Events", "end_time": 1443.0}, {"start_time": 1443.0, "title": "UCP Node Metrics", "end_time": 1492.0}, {"start_time": 1492.0, "title": "Install DTR from the UCP UI", "end_time": 1546.0}, {"start_time": 1546.0, "title": "DDC Templates for AWS and Azure", "end_time": 1595.0}, {"start_time": 1595.0, "title": "Pricing and Packaging Summary", "end_time": 3452}], "like_count": 7, "channel_follower_count": 103000, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@DockerInc", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10008/180RC4tlwIQ.tar.gz"}}