The first time I set it up, I realized I had a bunch of obsolete SSH keys in my account and I had no way to reach the system from the laptop I was using. As someone who obsesses over loose threads, I’m finding this all very satisfying.Īlthough, with that in mind, one important thing: if you haven’t played with Ubuntu for a while, head over to and make sure your SSH keys are up to date. Chances are you won’t need to SSH to the system anyway since it keeps itself up to date. In fact, you’re pretty much forced to: you don’t even get a login prompt. You can bury the thing somewhere and SSH to it from now on. There’s a simple setup process (configure networking, log in to your Ubuntu One account), and that’s it. Now that I figured out how to run it, I’ve been enjoying how this system is designed to minimize the time you need to spend with your device connected to a screen and keyboard like some kind of savage. (I didn’t feel like switching around SATA cables in my desktop, so I needed to write a different OS to a flash drive, boot from that on the NUC, transfer the Ubuntu Core image to there, then dd that image to the SSD. It’s easier if you do this while the drive is connected to another computer. Installing it is a bit surprising for the uninitiated because there isn’t really an install process: you just clone the image to the drive you want to boot from and you’re done. I installed Ubuntu Core 16, which is delightful. My only real complaint is the wifi hardware doesn’t work with older Linux kernels, but that wasn’t a big deal for my needs and I’m sure it will work in the future. It’s tiny, it’s quiet, and it looks okay too! (Just find somewhere to hide the power brick). In the end, I picked out an Intel NUC, and I threw in an old SSD and a stick of RAM: And besides, I like having a BeagleBoard free to mess around with now and then. I decided against both of those, because I wanted something with a bit more wiggle room. I dabbled with a BeagleBoard that I used for an embedded systems course, and I pondered a Raspberry Pi with a case. Some semblance of security, at least so a compromised service won’t put the rest of the system at risk.Compact, low power hardware that I can stick in a closet and forget about.Access over LAN from home, and over the Internet from anywhere else.Instant sync between devices for stuff I’m working on.Safe, convenient archiving for big files.I’m really happy with the result, so I thought I would explain it for anyone else who wants to do the same. I shouldn’t need to pay someone else for this.” I was also knee deep in a math course, so I felt like procrastinating. My annual Dropbox renewal date was coming up, and I thought to myself “I’m working with servers all the time. How can I fix everything so the container will auto-run on startup, but with the correct settings from the. It seems to be running fine now, but I think it has created a new container? When I run sudo docker container ls -a | grep syncthing, I get: 88e447e1cd78 syncthing/syncthing:latest "/bin/entrypoint.sh …" 27 minutes ago Up 27 minutes (healthy)ħdd04d0701a7 syncthing/syncthing:latest "/bin/entrypoint.sh …" 12 days ago Exited (0) 34 minutes ago Then running sudo ~/docker/syncthing/syncthing_run.sh. IDg=$(id -g $(logname)) # Saves the logged in user group in the IDg variable I was able to get it running again with all the settings by doing sudo docker stop syncthing to stop the already-running container, then removing the -name line from the script: IDu=$(id -u $(logname)) # Saves the logged in user id in the IDu variable When I tried to run syncthing from the syncthing_run.sh script, it complained that there was already a docker container running with the name syncthing and I needed to delete or rename the container in order to run with that name. sh file (no volumes, no other settings I think) - it was like it was running the container with only the default settings - wouldn't sync with any other devices, nothing other than the default share, etc. That worked great, but when I restarted the PC it auto-started the syncthing docker container, but without the extra settings in the. I followed the instructions here to install and run syncthing in a docker container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |