11–20 of 115 posts
It's interesting from a job market standpoint how little incentive there is to learn the basics when more and more we are seeing developers being made responsible for ops and admin tasks.
Honestly, it sounds more as if author is just not experienced enough to reap the rewards of containers/IaaC. Having some servers as pets is fine for time being, but after being used to the cattle little pesky issues & upkeep starts to annoy more and more and you either give up on it and leave neglected or slowly build up most of the infra you ran away from in the first place.
Once you work in enterprise IDC, setting up home labs is nothing but a liability. Unwanted stuff like UPS, cooling and more bills. I have one Intel NUC running FreeBSD 13 (dual SSD with 32 GB ram and Intel i7 CPU 8th GEN) with one jail and VM. It acts as a backup server for my Ubuntu laptop and MacBook pro. Nightly I dump data to cloud providers for offsite reasons. Finally, I set LXD, Docker and KVM on my Ubuntu dev…
I take your point and generally agree. Leave the major hardware to the actual data centers. Stuff at home should be either resume driven or very efficient.
Honestly, it sounds more as if author is just not experienced enough to reap the rewards of containers/IaaC. Having some servers as pets is fine for time being, but after being used to the cattle little pesky issues & upkeep starts to annoy more and more and you either give up on it and leave neglected or slowly build up most of the infra you ran away from in the first place.
It depends on your software selection. I run machines than i do updates on twice a year and thats all the maintenance they need. Less than a person-day per year!
I still don't know why you wouldn't use containers though, even if you dislike Docker, something like LXC makes everything oh-so neater.
Earlier quoted context omitted.
It depends on your software selection. I run machines than i do updates on twice a year and thats all the maintenance they need. Less than a person-day per year!
You're right, I might've extrapolated my usage/experience onto the author accidentally, maybe his use case is indeed different. I still don't know why you wouldn't use containers though, even if you dislike Docker, something like LXC makes everything oh-so neater.
Earlier quoted context omitted.
You're right, I might've extrapolated my usage/experience onto the author accidentally, maybe his use case is indeed different. I still don't know why you wouldn't use containers though, even if you dislike Docker, something like LXC makes everything oh-so neater.
I tried both Docker and Bubblewrap. Containers help with managing dependency creep, but if you avoid that in the first place, you don't need containers.
But even besides dependency creep, containers simplify your software env, simplify backups, migrations, permissions(although container are not replacement for secure isolation), file system access, network routing etc,etc,etc.
It's absolutely fine and I'd argue essential to know Linux system administration even for people who mostly work in the cloud. From my recent experience sys admin skills seem to be a lost art - people no longer have to care about the underpinnings of a Linux system and when problems hit it shows. It's interesting from a job market standpoint how little incentive there is to learn the basics when more and more we are…
I think this is to oldscool. You can still automate via Ansible, keep your playbooks and roles in Git and run VM's.