text stringlengths 9 408 |
|---|
[1564.28 --> 1571.80] Also, developers, if they're trying to do multiple different versions of an application development lifecycle all at once. |
[1571.80 --> 1578.70] You know, I've got three different builds and I'm trying to figure out which one is causing my production systems to go down. |
[1579.36 --> 1584.18] It's very easy to isolate and roll back a container that way because it's a declarative build. |
[1585.84 --> 1595.12] But I understand there are some more old school people around that don't like that approach because it is a little more opaque than you've been used to. |
[1595.12 --> 1605.86] However, I would say the reason it appears opaque is because perhaps you haven't quite taken the amount of time you need to to look into where that container originated from. |
[1607.52 --> 1614.74] And sometimes you can go and look at the Docker file in the open source community and see basically a Docker file is like a recipe. |
[1615.08 --> 1617.88] It's a glorified Bash script, essentially. |
[1618.74 --> 1624.06] And say apt install this package, create this user, install this particular library. |
[1624.06 --> 1628.66] And on the whole, those containers work pretty well. |
[1629.30 --> 1636.32] And this is a problem that used to exist that I haven't seen really be a problem for quite some time now. |
[1636.86 --> 1641.34] Is a lot of containers used to get uploaded to Docker Hub without a Docker file. |
[1641.52 --> 1645.62] So you had to just trust that they weren't going to run a crypto miner on you or something like that. |
[1645.70 --> 1648.00] And that problem largely seems to have gone away. |
[1649.00 --> 1651.20] There are lots of different places you can go. |
[1651.32 --> 1652.84] Linux server.io is one of them. |
[1652.84 --> 1657.34] You can go to obviously Docker's website as well for some documentation there. |
[1657.90 --> 1660.66] I'm going to say something that's probably not going to be popular. |
[1661.14 --> 1664.12] But I don't think containers are solution for everything. |
[1665.60 --> 1669.64] And it's Alex and I know containers are what puts roof over our heads. |
[1670.00 --> 1674.28] And I will honestly tell you again, I don't think containers are the solution for everything. |
[1674.28 --> 1681.26] You don't always need to build a server and install Docker or Podman and run a container on it. |
[1681.60 --> 1687.80] Sometimes you can just install the Debian, the dev files or the RPM files and configure it yourself. |
[1687.80 --> 1694.76] However, what containers do is it makes it easier to install services that work together. |
[1695.30 --> 1703.60] You know, if you have a service that goes out and queries, it does a search for a file, injects that download file into the download service. |
[1703.86 --> 1705.80] The download service then downloads the file. |
[1705.80 --> 1710.18] Another service grabs the file, reads the metadata, processes it. |
[1710.58 --> 1711.90] That's going to be really difficult. |
[1712.56 --> 1716.02] How do we know that all three of those services require the same version of LibC? |
[1716.42 --> 1721.54] How do we know that they require a specific version of Go, et cetera, et cetera? |
[1721.86 --> 1725.74] You don't want to run into the situation where you're constantly looking at dependencies. |
[1725.94 --> 1727.24] And that's what containers do. |
[1727.24 --> 1735.06] So if you're doing a standalone box or standalone application, yeah, you know, doing the FAD install is perfectly fine. |
[1735.36 --> 1742.38] But whenever you want to make sure that everything's going to work together and they're not going to butt heads, that's the real reason why containers were created. |
[1742.94 --> 1754.54] Now, to answer your question about Docker compose files, the way I do it, and I'm sure Alex does it his way, is if the services need to speak to each other, they're in the same compose file. |
[1754.54 --> 1758.26] I run 10 or 12 containers on my home lab. |
[1758.74 --> 1763.02] And if the service does not need to talk to each other, it gets its own compose. |
[1763.60 --> 1764.98] That's the way that I've always done it. |
[1765.36 --> 1771.74] There's no reason for me to do a Docker compose up with AdGuard in the same exact compose as Plex. |
[1772.22 --> 1773.40] They don't need to talk to each other. |
[1773.54 --> 1775.12] They don't need to be on the same Docker network. |
[1775.36 --> 1777.36] They can live in different Docker compose files. |
[1778.16 --> 1782.06] I once had a colleague tell me that Docker was a solution looking for a problem. |
[1782.06 --> 1793.86] Back then, this was like six years ago, I got really hot and steamy under the collar about this because Docker was the new hotness and I could see that it was going to solve all the world's problems. |
[1794.74 --> 1798.18] And with a little bit of hindsight, I think I kind of agree with him in some ways. |
[1798.96 --> 1805.96] It definitely has its use cases, but there are also places where VMs are probably better. |
[1805.96 --> 1812.74] Now coming to another part of Mike's question, he asks about tips for organizing container volumes on ZFS. |
[1813.60 --> 1816.14] I just create a data set per app, Mike. |
[1816.36 --> 1817.26] It's as simple as that. |
[1817.40 --> 1818.36] You can set quotas. |
[1818.68 --> 1823.12] You can do snapshots, you know, using Jim Salter's Sanoid tool. |
[1823.58 --> 1831.18] I have it set to do, I think, four hours worth of app data snapshots and then keep a daily snapshot and a monthly and an annual snapshot. |
[1831.18 --> 1846.60] So the only thing to be aware of there is if you're doing something like InfluxDB or some kind of really chatty time series container or database that generates a lot of data, those snapshots will take up a lot of space because of how copy on write works. |
[1846.78 --> 1851.18] So just make sure you're familiar with that concept before you dive into that one. |
[1852.18 --> 1854.72] Ivan writes in, do you guys host your own email server? |
[1855.10 --> 1856.46] And what are your thoughts on this? |
[1857.26 --> 1859.04] This might be a good idea for the show. |
[1859.04 --> 1863.14] I can tell you on a personal note, I love Gmail. |
[1863.70 --> 1864.62] Why do I love Gmail? |
[1865.54 --> 1866.28] It's easy. |
[1866.80 --> 1867.96] They read my emails. |
[1868.36 --> 1869.94] They tell me what I want to buy. |
[1870.36 --> 1873.70] It works on my phone and they give me a bunch of storage. |
[1874.78 --> 1879.46] But I can also tell you my private email is for my family only. |
[1880.04 --> 1883.70] I don't give it out to anybody who isn't related to me by marriage or by blood. |
[1884.58 --> 1887.26] And I run, therefore, my own email server. |
[1887.26 --> 1888.96] It's been $5 a month. |
[1889.10 --> 1889.92] It's on Linode. |
[1890.32 --> 1891.92] I recommend everybody use it. |
[1893.08 --> 1895.34] Do you, I want you to contact me for a job offer? |
[1896.10 --> 1896.88] I have a Gmail. |
[1897.32 --> 1899.08] Do I want to sign up for FPNL? |
[1899.70 --> 1900.02] Gmail. |
[1900.58 --> 1903.86] Do I want to send pictures to my mom, my kids? |
[1904.54 --> 1905.16] Personal email. |
[1905.16 --> 1907.66] I know that no one's ever going to get a hold of it. |
[1908.56 --> 1911.30] I know that I'm not going to have to worry about getting spam. |
[1912.14 --> 1914.96] Because, again, that's what Gmail is for. |
[1915.20 --> 1916.08] It's for spam filtering. |
[1916.98 --> 1919.28] My email that I host is for family only. |
[1919.86 --> 1922.22] It's for things that I want for me and only my family. |
[1923.04 --> 1925.30] And I recommend everybody to do the same. |
[1925.64 --> 1927.14] Again, it's $5 a month. |
[1927.76 --> 1928.92] Super easy to set up. |
[1928.92 --> 1930.14] I like Gmail, too. |
[1930.56 --> 1931.52] It just works. |
[1932.38 --> 1935.08] So Thomas writes in with networking on his mind. |
[1935.56 --> 1939.10] I wondered if either of you have touched VLANs on home networks. |
[1939.44 --> 1941.94] I just got two Netgear Smart PoE switches. |
[1942.08 --> 1944.28] And I'm thinking about how best to segment my network. |
[1944.70 --> 1947.40] I've got a NUC with Fedora on it and a Windows laptop. |
[1947.68 --> 1949.78] I've also got a NAS running some containers. |
[1949.78 --> 1954.74] And I make use of WireGuard and Plex on there as well. |
[1955.80 --> 1959.62] I've also got a Wi-Fi network that has a Google Nest and a pair of smart scales. |
[1960.48 --> 1963.28] Thanks for an interesting show and inspiration for my home network. |
[1963.58 --> 1963.86] Thomas. |
[1964.56 --> 1968.10] VLANs and the home network is an interesting topic. |
[1969.12 --> 1973.20] I think for 90 plus percentage of the world, you don't need them. |
[1974.14 --> 1977.84] Until you start considering IoT devices and how insecure they are. |
[1977.84 --> 1979.96] And who can get access to them. |
[1980.86 --> 1987.04] And the second you have IoT devices that are a huge gaping security hole, you need to segment them. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.