text stringlengths 9 408 |
|---|
[1871.16 --> 1879.20] But unfortunately, because that version of Docker is so old, it means a lot of the newer features in Docker Compose aren't supported. |
[1879.46 --> 1883.90] So you then think to yourself, hmm, I could upgrade the version of Docker, couldn't I? |
[1884.02 --> 1885.16] And yes, you can. |
[1885.24 --> 1889.00] There is a GitHub repo to do that in an unsupported fashion. |
[1889.00 --> 1896.98] And then you quickly run into all sorts of problems trying to figure out how networking bridging works and all that kind of stuff and wish you'd never bothered. |
[1896.98 --> 1903.92] So my recommendation with Docker would be to just stick to the UI on the Synology and it will just work brilliantly. |
[1904.78 --> 1912.46] And then if you're a crazy kid like Alex, you could just end up using your Synology as an iSCSI endpoint and point your VMware infrastructure at it. |
[1912.94 --> 1913.78] That's true, actually. |
[1913.88 --> 1918.60] Yeah, you see Synologies in the backgrounds of so many tech YouTuber videos. |
[1918.60 --> 1923.84] Network Chuck, Lawrence Systems, Tom from Lawrence Systems. |
[1924.04 --> 1926.40] They've all got Synologies blinking away in the background. |
[1926.52 --> 1931.62] And I've often wondered, what are these guys that surely know better, right? |
[1931.84 --> 1932.52] In air quotes. |
[1932.96 --> 1934.90] What are they all doing with their Synologies? |
[1935.04 --> 1941.08] And it turns out, actually, if you fill this sucker up with SSDs and put a 10 gig networking card in there, |
[1941.08 --> 1949.62] you can get some seriously good performance over iSCSI with VMware, which Synology have worked very hard to get the official certification for. |
[1950.04 --> 1954.14] Yeah, I remember we were talking to Wendell and he even thought that was pretty remarkable back in the day. |
[1954.70 --> 1955.94] But it is pretty good to see it. |
[1955.98 --> 1957.64] And a nice little HomeLab addition. |
[1958.00 --> 1965.72] So if you have something like an Intel NUC that doesn't have much storage and you want a cheap way to add, you know, six, eight or more drives, |
[1965.72 --> 1975.04] because Synology offer a lot of different products, buy Synology, use iSCSI, and then your NUC suddenly has, you know, 20 terabytes to go at. |
[1975.52 --> 1976.20] I can see it too. |
[1976.30 --> 1982.12] Like, maybe one day I'll have all these Raspberry Pis and then there'll just be one centralized storage. |
[1982.50 --> 1984.04] To be able to support VMware is pretty great. |
[1984.16 --> 1991.24] But when you were messing around with this, one thing I didn't hear you talk about was if you dug into what your backup options would be, |
[1991.24 --> 1996.86] if you felt like you were limited, maybe by the DSM, by what your backup options could be. |
[1997.00 --> 1998.22] What was that experience like? |
[1998.50 --> 1999.64] Well, it's not running ZFS. |
[1999.96 --> 2005.88] So I needed a way in which to do version snapshots and incremental backups. |
[2006.58 --> 2013.30] Incremental backups are really important because rather than sending the entire file system every single time, |
[2013.84 --> 2016.28] it only sends the bits and bytes that have changed. |
[2016.28 --> 2024.76] Now, ZFS does this at the block level, but because I'm going from ZFS to ButterFS, there's no mechanism in place to do that. |
[2025.34 --> 2031.46] Now, I could use R-Sync, but then it's going through and it's checking MD5 hashes every time, and it can be a bit slow and a bit clunky. |
[2032.24 --> 2034.32] And I tripped over something called Minio. |
[2034.92 --> 2038.22] I actually mentioned this, I think, with the orange one last week. |
[2038.22 --> 2042.66] I tripped over Minio, which is a S3 front end. |
[2043.02 --> 2049.62] Now, this provides the S3 object storage API on your LAN, effectively, backed by your own storage. |
[2050.14 --> 2061.50] Now, the advantage that that gives you is that you can use a tool such as Restic to do incremental version snapshot backups to this S3 endpoint backed by the Synology. |
[2061.50 --> 2066.56] All right, so pause, because this is a big deal, and this is probably something we should dedicate an entire episode to, |
[2066.68 --> 2072.90] but this lets you build your own S3 object storage on your LAN or maybe up in the cloud. |
[2073.40 --> 2075.92] There's a lot of ways you could use this if you think about it. |
[2076.58 --> 2080.30] Yeah, we should come back to this as a separate topic, but okay, so let me unpack this. |
[2080.32 --> 2089.32] So you have something like this set up on your LAN running, exposing some storage that you're then making available to the DSM software, or how does this work? |
[2089.32 --> 2090.98] Minio is running as a container. |
[2091.18 --> 2096.78] That's then backed by a volume mount to one of the volumes on the Synology itself. |
[2097.02 --> 2102.22] Lots of volumes terms going on here, but that's where it gets a little confusing. |
[2102.96 --> 2105.96] So essentially what happens is Minio is running as a container. |
[2106.38 --> 2117.60] It presents itself as an API that I can then call from Restic, and Restic will then just store the data on those S3 buckets as objects. |
[2117.60 --> 2124.00] That's worth doing too, Alex, because it seems like you could use that for other stuff in the future as well, because there's a lot of things that will just plug right into that. |
[2124.18 --> 2127.72] It does free you up from the ZFS kind of train, if you like. |
[2127.72 --> 2138.06] So if something like ZFS.rent isn't up your street, and you want to host just a few hundred megabytes of files, then something like Restic is going to do you really well. |
[2138.54 --> 2141.62] One of the most difficult parts of using Restic is configuring it. |
[2142.08 --> 2148.66] Now, I came across a project this week which solves that problem in a really beautiful way called AutoRestic. |
[2148.66 --> 2158.60] Now, there's a link to this thing in the show notes, but essentially what happens is you define the locations and the backends in a YAML file, and you're done. |
[2159.08 --> 2160.22] That's not so bad to manage. |
[2160.38 --> 2164.10] I mean, that sounds like something that I could probably wrap my head around. |
[2164.34 --> 2177.26] What's really nice as well is if you just have a local backend, which is just some dumb USB hard drive, you can actually have as one of your backends just HDD type local path, my external storage. |
[2177.26 --> 2178.92] And it's as simple as that. |
[2179.24 --> 2182.50] Oh, although my backend is never dumb, but that does seem really nice. |
[2183.04 --> 2184.86] I didn't mean it as an insult, darling. |
[2186.72 --> 2190.54] There's a bunch of other cool stuff that AutoRestic supports as well, like hooks. |
[2190.74 --> 2201.80] So if you want to perform some commands before or after a specific backup, let's say you want to delete some files after a backup's happened, for example, you can do that using the hooks that are built into AutoRestic. |
[2202.22 --> 2204.40] You can also exclude files as well. |
[2204.84 --> 2206.20] And there is a forget policy. |
[2206.20 --> 2224.56] So one of the favorite things about ZFS Send for me is when I use Jim Salter's Sanoid tool, it has a policy-driven snapshot engine, which will automatically keep the last hour or the last six hours and then the last six days and then the last six weeks and then the last six months. |
[2224.72 --> 2227.88] It will keep one snapshot from each of those different timestamps. |
[2227.88 --> 2237.84] AutoRestic also has a forget and prune policy engine built right into it, which you configure again in the YAML right next to the location that you're defining. |
[2238.26 --> 2240.96] It's just, it's the way Restic should work. |
[2241.44 --> 2242.44] Yeah, that does sound nice. |
[2242.90 --> 2243.60] Well, very good. |
[2243.60 --> 2247.76] We will have a link to that at selfhosted.show slash 43. |
[2248.14 --> 2252.38] Now, before we go, Alex, Jace Novell wrote in on the Discord. |
[2252.62 --> 2255.16] So I guess that's more like sent a message on Discord. |
[2255.42 --> 2257.56] And then we thought that's a good question to read on the show. |
[2257.66 --> 2261.72] But he says, I'm working through the planning stages of building a new home. |
[2262.06 --> 2263.54] Oh, I love that. |
[2263.64 --> 2263.88] Yeah, Lee. |
[2263.88 --> 2264.78] Oh, I'm envious. |
[2265.12 --> 2265.28] Yeah. |
[2265.62 --> 2275.54] He writes, if you're all starting from scratch, how would you design a smart home that would get the wife approval factor, but at the same time, not be too much overkill? |
[2275.90 --> 2280.74] Well, that actually feels like that's how you achieve the wife approval factor is by not going overkill. |
[2280.88 --> 2283.26] But I get the spirit of his question. |
[2283.38 --> 2289.22] Like, what's a reasonable kind of build it in while I have the opportunity, but not go excessive? |
[2289.82 --> 2292.14] Automated flamethrowers on the driveway should do the trick. |
[2292.14 --> 2295.52] Right, and don't forget laser pointers on articulating arms. |
[2296.38 --> 2301.16] So that way you can, you know, you can just put that out there and that way the pets stay entertained. |
[2301.32 --> 2307.24] No, but really thinking about it, it comes down in my mind, like the first place I go to is just solid networking. |
[2307.58 --> 2312.12] Whilst you've got those walls open, run as many high quality cables as you can. |
[2312.32 --> 2312.50] Yeah. |
[2312.62 --> 2315.24] I would suggest starting with Cat6A as a minimum. |
[2315.86 --> 2317.74] Yes, it could be considered a little bit overkill. |
[2317.74 --> 2324.38] You know, 5E will do quite comfortably gigabit ethernet and even, it'll even do 10 gig over a very short distance. |
[2324.66 --> 2327.94] But Cat6A will give you 10 gig guaranteed. |
[2328.20 --> 2331.30] I think it's like three or 500 feet, something like that. |
[2331.30 --> 2341.90] And if you're thinking about the lifetime of a house, which could be 50 plus years, you really want to put in there as good as you can afford to at the time you're building it. |
[2341.94 --> 2347.70] Because having retrofitted a couple of houses with ethernet cable, let me tell you, pulling cable is no fun. |
[2347.70 --> 2354.20] It's how you'll do everything from cameras to smoke detectors to sensors to Wi-Fi endpoints. |
[2354.90 --> 2359.70] Everything's better with ethernet or just workstations, televisions, media set top boxes. |
[2360.16 --> 2362.10] You'll never beat wired. |
[2362.26 --> 2366.60] As good as wireless gets, it cannot just beat a physical copper connection. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.