1 - slightly wrong. You're not using just system resources. A container uses the whole of the host's OS kernel. You can't run any container on any OS regardless. For example, to run a docker container in Windows you need an extra abstraction, by default a HyperV VM or the kernel provided by the WSL2 (which is a bit closer to the proper OS). For example on Windows if you have HyperV & WSL2 disabled, Docker will complain it can't run.
3 - ok, but you might better ask "what's the relationship between image and container" ?
4 - it's a bad interview question format because it's a leading question. Somehow who doesn't know still has a 50% chance of getting it right since it's a yes/no question. You should ask what are the accepted formats for a compose file.
8 - pointless question. You're asking about platforms so the plain answer is Linux/Unix , Windows, Mac. The listing of cloud providers is pointless, Docker runs on the OS installed on their VMs, nothing to do with the cloud provider itself. The listing of distros is also pointless ... you're asking if the candidate knows all the Linux distros? You missed Mandriva ... is that bad?
17 - create container? a container is a running image. I find the "create" bit somewhat meaningless since it's part of running it.
19 - starts or runs? depends_on ensures the container will start but might not achieve a running state before the next one. A healthcheck improves the chances of that.
If you're going to correct a post someone puts their hardwork in making for others to learn and strengthen their understanding, you might as well correct it respectfully.
If you had perfect knowledge of this topic why didn't you write the post yourself??
Better still you might as well have answered the 20 more questions with no answers.
You don't have to have perfect knowledge to point out glaring mistakes. It's like seeing someone trying to nail something using a shoe instead of a hammer who says only someone who has been a master carpenter for 20 years is allowed to point out that a hammer is a better tool.
Hard work is a relative matter. For example, the fact that Docker uses the host kernel is in the documentation. It's better to provide the questions as-is and let people learn by doing the research (the questions themselves are good) rather than provide wrong/misleading answers.
Seems like you didn't read the part where I said you should correct respectfully
You're contradicting yourself saying "the questions themselves are good" when you literally called them "wrong", "bad interview question", "pointless".
If you feel a post is "wrong", "bad" or "pointless", there's nothing bad, its your view. But you should atleast correct respectfully if you're going to correct.
There's a difference between question and answer. One is pointless and another could be improved by asking it differently. Some of the answers are wrong, which is what I specifically said. The questions are ok as interview questions.
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.
1 - slightly wrong. You're not using just system resources. A container uses the whole of the host's OS kernel. You can't run any container on any OS regardless. For example, to run a docker container in Windows you need an extra abstraction, by default a HyperV VM or the kernel provided by the WSL2 (which is a bit closer to the proper OS). For example on Windows if you have HyperV & WSL2 disabled, Docker will complain it can't run.
3 - ok, but you might better ask "what's the relationship between image and container" ?
4 - it's a bad interview question format because it's a leading question. Somehow who doesn't know still has a 50% chance of getting it right since it's a yes/no question. You should ask what are the accepted formats for a compose file.
8 - pointless question. You're asking about platforms so the plain answer is Linux/Unix , Windows, Mac. The listing of cloud providers is pointless, Docker runs on the OS installed on their VMs, nothing to do with the cloud provider itself. The listing of distros is also pointless ... you're asking if the candidate knows all the Linux distros? You missed Mandriva ... is that bad?
17 - create container? a container is a running image. I find the "create" bit somewhat meaningless since it's part of running it.
19 - starts or runs? depends_on ensures the container will start but might not achieve a running state before the next one. A healthcheck improves the chances of that.
If you're going to correct a post someone puts their hardwork in making for others to learn and strengthen their understanding, you might as well correct it respectfully.
If you had perfect knowledge of this topic why didn't you write the post yourself??
Better still you might as well have answered the 20 more questions with no answers.
You don't have to have perfect knowledge to point out glaring mistakes. It's like seeing someone trying to nail something using a shoe instead of a hammer who says only someone who has been a master carpenter for 20 years is allowed to point out that a hammer is a better tool.
Hard work is a relative matter. For example, the fact that Docker uses the host kernel is in the documentation. It's better to provide the questions as-is and let people learn by doing the research (the questions themselves are good) rather than provide wrong/misleading answers.
Seems like you didn't read the part where I said you should correct respectfully
You're contradicting yourself saying "the questions themselves are good" when you literally called them "wrong", "bad interview question", "pointless".
If you feel a post is "wrong", "bad" or "pointless", there's nothing bad, its your view. But you should atleast correct respectfully if you're going to correct.
There's a difference between question and answer. One is pointless and another could be improved by asking it differently. Some of the answers are wrong, which is what I specifically said. The questions are ok as interview questions.