Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Does it solve any problems? How is a statically-linked executable liable to break from changes in an OS it doesn't even use?


Badly designed apps can break in all sorts of fun ways without docker

- Check for processes called "sleep", exit if such process exist (or try to kill it).

- Reset $PATH to default value then expect to find a _very_ specific ancient version of system utilities there.

- Create files in /tmp with fixed names. Fail if they already exist. Forget to delete them on failure.

- Walk entire filesystem searching for something. Crash on broken symlinks.

- Enumerate network interfaces. Crash if more than 7 are present.

- Hardcode _both_ specific user name and associated UID.

- Put temp files all over place, including into application directory

- Ignore $HOME and use homedir from /etc/passwd, then create lock/config file under homedir. And you want to run two instance of this app in parallel.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: