Anthony E. Nocentino

Hi there, Filestream is not supported in SQL Server on Linux and Docker containers. Check out this link for more details - [https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-editions-and-components-2019?view=sql-server-ver15#Unsupported](https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-editions-and-components-2019?view=sql-server-ver15#Unsupported)

Ah my bad then, I assumed Linux container :) I don't have any experience with the SQL Windows containers.

Perhaps this post could help. I’ve seen this issue when the database being restored is larger than the available space in Docker. https://danielssilva.dev/2019-09-09-MODIFY-FILE-encountered-operating-system-error-31(A-device-attached-to-the-system-is-not-functioning.)-while-attempting-to-expand-the-physical-file/

What’s the length of the hostname for the container? There’s an issue with SQL Agent on Linux cannot support hostnames linger than 15 characters. Anthony On May 3, 2020, at...

When running with CPU limits, any process running inside a container will see all of the CPUs but the underlying Linux kernel will ensure that the process is only consuming...

Due to the architecture of SQL Server on Linux (SQLPAL) it requires 2GB memory. Check out this link here for system requirements. [https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver15#system] This requirement applies to running SQL Server...

As a workaround, you could set the hostname field on the Pod Spec for your Deployment. This will set the hostname in the pod and will be what’s set for...

docker logs "container_name" is helpful in this situation. SQL Server on Linux will write to stdout and perhaps will report your error. You can access this output with the docker...

This might be the virtualization issue fixed in 10.15.6. Perhaps patch your base OS. Thanks, Anthony Anthony E. Nocentino Senior Technical Fellow Centino Systems www.centinosystems.com | Blog | LinkedIn |...