text
stringlengths
9
408
[2477.74 --> 2479.32] in terms of security.
[2479.72 --> 2480.22] You can mount it
[2480.22 --> 2480.76] through a proxy.
[2481.16 --> 2481.54] That's probably
[2481.54 --> 2482.26] the safest way
[2482.26 --> 2482.82] to do that.
[2483.60 --> 2484.08] But essentially,
[2484.26 --> 2484.78] what it does
[2484.78 --> 2485.24] is it lists
[2485.24 --> 2486.04] all of your containers
[2486.04 --> 2487.30] on the left-hand side.
[2487.42 --> 2488.02] It says that,
[2488.14 --> 2488.32] you know,
[2488.34 --> 2488.84] you can see
[2488.84 --> 2490.02] which ones are running,
[2490.76 --> 2492.02] when their last restart
[2492.02 --> 2492.28] was,
[2492.30 --> 2492.98] all that kind of stuff.
[2493.08 --> 2493.96] But then you just click
[2493.96 --> 2494.54] on the container
[2494.54 --> 2495.52] and it shows you the logs
[2495.52 --> 2496.22] as if you were doing
[2496.22 --> 2496.90] Docker logs
[2496.90 --> 2498.46] name of service.
[2499.20 --> 2500.30] And that's pretty much it.
[2500.66 --> 2501.48] That's all it does,
[2501.52 --> 2502.06] but it does it
[2502.06 --> 2502.42] really,
[2502.54 --> 2502.88] really well.
[2502.88 --> 2503.84] Yeah,
[2503.90 --> 2504.48] and it helps,
[2504.60 --> 2505.96] it helps you search
[2505.96 --> 2506.68] through the log
[2506.68 --> 2507.44] and find stuff.
[2507.52 --> 2508.84] It has this really nice
[2508.84 --> 2510.26] real-time search function
[2510.26 --> 2512.08] that is super useful.
[2512.32 --> 2513.68] And after my experience
[2513.68 --> 2515.24] I had earlier
[2515.24 --> 2516.48] with realizing
[2516.48 --> 2517.48] that one of my containers
[2517.48 --> 2518.36] was actually
[2518.36 --> 2519.52] restarting frequently,
[2520.02 --> 2520.86] kind of realized
[2520.86 --> 2521.46] I could use something
[2521.46 --> 2522.00] like this.
[2522.12 --> 2522.82] So I'm going to take
[2522.82 --> 2523.44] a look at Dozzle
[2523.44 --> 2525.76] and maybe,
[2525.96 --> 2526.78] maybe I'll throw it
[2526.78 --> 2527.24] on a machine.
[2527.66 --> 2528.82] I talked about this one
[2528.82 --> 2529.82] on Linux Action News,
[2529.98 --> 2530.96] but it's worth noting here
[2530.96 --> 2531.56] since we're kind of
[2531.56 --> 2531.96] on a roll.
[2531.96 --> 2533.72] Docker Compose
[2533.72 --> 2534.82] is changing
[2534.82 --> 2535.54] from like a
[2535.54 --> 2537.30] standalone Python thing
[2537.30 --> 2540.32] to inside Docker itself.
[2540.86 --> 2541.44] So I think the way
[2541.44 --> 2542.00] it's going to work,
[2542.14 --> 2542.28] Alex,
[2542.34 --> 2543.04] is existing
[2543.04 --> 2544.34] Docker Compose commands
[2544.34 --> 2545.14] will just kind of
[2545.14 --> 2546.02] map to the new
[2546.02 --> 2547.56] Docker Compose commands.
[2548.00 --> 2548.74] But instead of it being
[2548.74 --> 2550.06] like Docker-Compose,
[2550.14 --> 2551.10] the new proper syntax
[2551.10 --> 2551.52] will just be
[2551.52 --> 2553.24] Docker space-Compose
[2553.24 --> 2554.40] because it's now
[2554.40 --> 2555.42] inside the Docker app
[2555.42 --> 2556.40] and not a separate thing.
[2557.12 --> 2557.22] Yeah,
[2557.26 --> 2558.00] just as if Docker
[2558.00 --> 2558.66] needed to be
[2558.66 --> 2559.64] even more monolithic.
[2559.64 --> 2561.20] They are un-breaking
[2561.20 --> 2562.90] out the separate project
[2562.90 --> 2563.98] that is Docker Compose
[2563.98 --> 2565.70] and bringing it in-house.
[2565.88 --> 2566.58] So I think this is
[2566.58 --> 2568.04] largely a bit of tech debt
[2568.04 --> 2568.98] that they're addressing here.
[2569.54 --> 2570.32] If you go way,
[2570.38 --> 2571.04] way, way back
[2571.04 --> 2571.78] in the annals,
[2572.28 --> 2572.98] Docker Compose
[2572.98 --> 2574.10] actually started its life
[2574.10 --> 2574.60] as a project
[2574.60 --> 2575.30] named Fig
[2575.30 --> 2576.62] and then it was
[2576.62 --> 2578.06] renamed to Docker Compose
[2578.06 --> 2578.88] and it became
[2578.88 --> 2579.78] what we know today.
[2580.88 --> 2581.30] You know,