Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
Containers are what you make of them. At the very least, they can be useful for doing code-testing (regardless of where that code is going to run). Basically:
Spin up a testing-harness container
Make your code visible/testable to the container
Invoke testing-harness against the container
E.g., if I have code where I would normally just say/pray "this works on <DISTRO_A> and should be portable to <DISTRO_B>", I can spin up a <DISTRO_B>-flavored container and run it in that context without having to stand up a whole VM to do so.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Containers are what you make of them. At the very least, they can be useful for doing code-testing (regardless of where that code is going to run). Basically:
E.g., if I have code where I would normally just say/pray "this works on <DISTRO_A> and should be portable to <DISTRO_B>", I can spin up a <DISTRO_B>-flavored container and run it in that context without having to stand up a whole VM to do so.