There isn't a hard-and-fast rule, and as I mentioned when a similar question arose on Meta Stack Overflow, topic overlap is possible and permitted.

That said, the very rough boundary that I usually look at is:

• If it happens inside the container, it is probably not for Server Fault.
• If it happens outside the container, it probably is something for Server Fault.

Some examples:

• Deploying the hardware and storage which a production Docker uses most likely belongs here. For instance, setting up Docker to store volumes on an NFS server.
• Connecting Docker to a production network probably belongs here. For instance, bridging Docker to a physical switch; configuring IP address ranges, etc.
• Fetching metadata about the Docker environment (e.g. the IP address of a related container) from within your program running in a container most likely belongs on Stack Overflow.
• Learning how various basic Linux commands work is best asked on Super User or Unix & Linux. (And U&L is probably where I would recommend you take your specific question first, as it doesn't seem to be about programming or Docker-specific.)
• Architecting the environment that a container provides to the application it runs is an area of overlap. It's not really programming, but programmers are often (usually wrongly) expected to do it. It's closer to operations, and has many operations issues programmers are ill-equipped to handle, but administrators often don't or aren't allowed to participate (which is also wrong). Worse, Docker's design encourages this. But that's another discussion... For topicality, as I said before, make your best guess and bring your hazmat suits.

There isn't a hard-and-fast rule, and as I mentioned when a similar question arose on Meta Stack Overflow, topic overlap is possible and permitted.

That said, the very rough boundary that I usually look at is:

• If it happens inside the container, it is probably not for Server Fault.
• If it happens outside the container, it probably is something for Server Fault.

Some examples:

• Deploying the hardware and storage which a production Docker uses most likely belongs here. For instance, setting up Docker to store volumes on an NFS server.
• Connecting Docker to a production network probably belongs here. For instance, bridging Docker to a physical switch; configuring IP address ranges, etc.
• Fetching metadata about the Docker environment (e.g. the IP address of a related container) from within your program running in a container most likely belongs on Stack Overflow.
• Learning how various basic Linux commands work is best asked on Super User or Unix & Linux. (And U&L is probably where I would recommend you take your specific question first, as it doesn't seem to be about programming or Docker-specific.)
• Architecting the environment that a container provides to the application it runs is an area of overlap. It's not really programming, but programmers are often (usually wrongly) expected to do it. It's closer to operations, and has many operations issues programmers are ill-equipped to handle, but administrators often don't or aren't allowed to participate (which is also wrong). Worse, Docker's design encourages this. But that's another discussion... For topicality, as I said before, make your best guess and bring your hazmat suits.

There isn't a hard-and-fast rule, and as I mentioned when a similar question arose on Meta Stack Overflow, topic overlap is possible and permitted.

That said, the very rough boundary that I usually look at is:

• If it happens inside the container, it is probably not for Server Fault.
• If it happens outside the container, it probably is something for Server Fault.

Some examples:

• Deploying the hardware and storage which a production Docker uses most likely belongs here. For instance, setting up Docker to store volumes on an NFS server.
• Connecting Docker to a production network probably belongs here. For instance, bridging Docker to a physical switch; configuring IP address ranges, etc.
• Fetching metadata about the Docker environment (e.g. the IP address of a related container) from within your program running in a container most likely belongs on Stack Overflow.
• Learning how various basic Linux commands work is best asked on Super User or Unix & Linux. (And U&L is probably where I would recommend you take your specific question first.)
• Architecting the environment that a container provides to the application it runs is an area of overlap. It's not really programming, but programmers are often (usually wrongly) expected to do it. It's closer to operations, and has many operations issues programmers are ill-equipped to handle, but administrators often don't or aren't allowed to participate (which is also wrong). Worse, Docker's design encourages this. But that's another discussion... For topicality, as I said before, make your best guess and bring your hazmat suits.

There isn't a hard-and-fast rule, and as I mentioned when a similar question arose on Meta Stack Overflow, topic overlap is possible and permitted.

That said, the very rough boundary that I usually look at is:

• If it happens inside the container, it is probably not for Server Fault.
• If it happens outside the container, it probably is something for Server Fault.

Some examples:

• Deploying the hardware and storage which a production Docker uses most likely belongs here. For instance, setting up Docker to store volumes on an NFS server.
• Connecting Docker to a production network probably belongs here. For instance, bridging Docker to a physical switch; configuring IP address ranges, etc.
• Fetching metadata about the Docker environment (e.g. the IP address of a related container) from within your program running in a container most likely belongs on Stack Overflow.
• Learning how various basic Linux commands work is best asked on Super User or Unix & Linux. (And U&L is probably where I would recommend you take your specific question first, as it doesn't seem to be about programming or Docker-specific.)
• Architecting the environment that a container provides to the application it runs is an area of overlap. It's not really programming, but programmers are often (usually wrongly) expected to do it. It's closer to operations, and has many operations issues programmers are ill-equipped to handle, but administrators often don't or aren't allowed to participate (which is also wrong). Worse, Docker's design encourages this. But that's another discussion... For topicality, as I said before, make your best guess and bring your hazmat suits.