![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/159-0-RHEL8-podman-SQL-e1563971287209.jpg\")
<\/p>\nHaving a fresh install of RHEL8 on my lab environment, I was curious to take a look at new containerization stuff from Red Hat in the context of SQL Server 2019. Good chances are the future version of SQL Server should be available and supported on with the latest version of Red Hat but for now this blog post is purely experimental. This time I wanted to share with you some thoughts about the new Podman command.<\/p>\n
<\/p>\n
First of all, we should be aware that since RHEL8 Red Hat decided to replace docker with CRI-O\/podman in order to provide a \u201cdaemonless\u201d container world and especially for Kubernetes. By 2016, Kubernetes project introduced the <\/span><\/span>Container Runtime Interface<\/span><\/a> (CRI).\u00a0 Basically, with CRI, Kubernetes can be container runtime-agnostic. <\/span><\/span>CRI-O<\/span><\/a> that is an open source project initiated by Red Hat the same year that gives the ability to run containers directly from Kubernetes without any unnecessary code or tooling as long as the container remains OCI-compliant. Because Docker is not implemented anymore (and officially not supported) by Red Hat since RHEL8, we need a client tool for working with containers and this is where <\/span><\/span>Podman<\/span><\/a> steps in. To cut the story short, Podman implements almost all the Docker CLI commands and more. <\/span><\/span><\/span><\/p>\n So, let\u2019s have an overview of Podman commands through the installation of a SQL Server 2019 based container. It is worth noting that Podman is not intended to be used in the context of a “standalone” container environnement and should be used with an container orchestrator like K8s or an orchestration platform like OpenShift.\u00a0 That said,\u00a0 let\u2019s first create a host directory to persist the SQL Server database files.<\/span><\/span><\/p>\n Then let\u2019s download the SQL Server 2019 RHEL image. We will use the following Podman command:<\/span><\/span><\/p>\n Note that if you\u2019re already comfortable with the Docker commands, the shift to Podman will be easy thanks to the similarity between the both tools. To get information of the new fresh image, we will use the following Podman command:<\/span><\/span><\/p>\n As show above, Podman uses the CRI-O back-end store directory with the \/var\/lib\/containers path, instead of using the Docker default storage location (\/var\/lib\/docker).<\/span><\/span><\/p>\n Go ahead and let\u2019s take a look at the Podman info command:<\/span><\/span><\/p>\n The same kind of information is provided by the Docker info command including the runtime and the graph driver name that is overlay in my case. <\/span><\/span>Generally speaking, creating and getting information of a container with Podman is pretty similar to what we may use with the usual Docker commands. Here\u00a0 for instance the command to spin up a SQL Server container based on the RHEL image:<\/span><\/span><\/p>\n Here comes the interesting part. Looking at the pstree output we may notice that there is not dependencies with any (docker) daemon with CRI-O implementation. Usually with the Docker implementation we retrieve the containerd daemon and the related shim for the process within the tree.\u00a0 <\/span><\/span><\/span><\/p>\n By using the runc command below, we may notice the MSSQL container (identified by the ID here) is actually running through CRI-O and runc runtime. <\/span><\/span><\/p>\n Let\u2019s have a look at the existing namespace. The 9449 PID corresponds to the SQL Server process running in isolation mode through Linux namespaces.<\/span><\/span><\/p>\n We can double check that the process belongs to the SQL Server container by using the nsenter command:<\/span><\/span><\/p>\n Well, we used different Podman commands to spin up a container that meets the OCI specification like Docker. For a sake of curiosity, let\u2019s build a custom image from a Dockerfile. In fact, this is a custom image we developed for customers to meet our best practices requirements.\u00a0 <\/span><\/span><\/span><\/p>\n To build an image from a Dockerfile the corresponding Podman command is as follow:<\/p>\n The image built is now available in the local repository:<\/p>\n The next step will consist in spinning up a SQL Server container based on this new image. Note that I used a custom parameter DMK=Y to drive the creation of the DMK maintenance tool in our case which including the deployment of a custom dbi_tools database ans related objects that carry out the database maintenance.<\/span><\/span><\/p>\n Let\u2019s check if the dbi_tools has been created during the container runtime phase:<\/span><\/span><\/p>\n Finally, to make the transition with a future blog post, the Podman tool comes with extra commands (under development) that is not available with Docker CLI.\u00a0<\/span><\/span>The following example generates a YAML deployment file and the corresponding service from an existing container. Please note however that containers with volumes are not supported yet. <\/span><\/span><\/p>\n The container definition is a follows:<\/p>\n And we get the corresponding YAML file generated by the Podman command:<\/p>\n By default the service type NodePort has been created by the command. This latest command needs further testing for sure!<\/p>\n See you<\/p>\n By David Barbarin<\/span><\/p>\n","protected":false},"excerpt":{"rendered":" Having a fresh install of RHEL8 on my lab environment, I was curious to take a look at new containerization stuff from Red Hat in the context of SQL Server 2019. Good chances are the future version of SQL Server should be available and supported on with the latest version of Red Hat but for […]<\/p>\n","protected":false},"author":26,"featured_media":12669,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,1320,1504,99],"tags":[720,151,601,1646,1502,1457],"type_dbi":[],"class_list":["post-12668","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","category-devops","category-docker","category-sql-server","tag-container","tag-devops","tag-docker","tag-podman","tag-rhel-8","tag-sql-server-2019"],"acf":[],"yoast_head":"\n$ sudo mkdir -p \/var\/mssql\/data\n$ sudo chmod 755 -R \/var\/mssql\/data<\/pre>\n
$ sudo podman pull mcr.microsoft.com\/mssql\/rhel\/server:2019-CTP3.1\nTrying to pull mcr.microsoft.com\/mssql\/rhel\/server:2019-CTP3.1...Getting image source signatures\nCopying blob 079e961eee89: 70.54 MiB \/ 70.54 MiB [========================] 1m3s\nCopying blob 1b493d38a6d3: 1.20 KiB \/ 1.20 KiB [==========================] 1m3s\nCopying blob 89e62e5b4261: 333.24 MiB \/ 333.24 MiB [======================] 1m3s\nCopying blob d39017c722a8: 174.82 MiB \/ 174.82 MiB [======================] 1m3s\nCopying config dbba412361d7: 4.98 KiB \/ 4.98 KiB [==========================] 0s\nWriting manifest to image destination\nStoring signatures\ndbba412361d7ca4fa426387e1d6fc3ec85e37d630bfe70e6599b5116d392394d<\/pre>\n
$ sudo podman images\nREPOSITORY TAG IMAGE ID CREATED SIZE\nmcr.microsoft.com\/mssql\/rhel\/server 2019-CTP3.1 dbba412361d7 3 weeks ago 1.79 GB\n$ sudo podman inspect dbba\n\u2026\n\"GraphDriver\": {\n \"Name\": \"overlay\",\n \"Data\": {\n \"LowerDir\": \"\/var\/lib\/containers\/storage\/overlay\/b2769e971a1bdb62f1c0fd9dcc0e9fe727dca83f52812abd34173b49ae55e37d\/diff:\/var\/lib\/containers\/storage\/overlay\/4b0cbf0d9d0ff230916734a790f47ab2adba69db44a79c8eac4c814ff4183c6d\/diff:\/var\/lib\/containers\/storage\/overlay\/9197342671da8b555f200e47df101da5b7e38f6d9573b10bd3295ca9e5c0ae28\/diff\",\n \"MergedDir\": \"\/var\/lib\/containers\/storage\/overlay\/b372c0d6ff718d2d182af4639870dc6e4247f684d81a8b2dc2649f8517b9fc53\/merged\",\n \"UpperDir\": \"\/var\/lib\/containers\/storage\/overlay\/b372c0d6ff718d2d182af4639870dc6e4247f684d81a8b2dc2649f8517b9fc53\/diff\",\n \"WorkDir\": \"\/var\/lib\/containers\/storage\/overlay\/b372c0d6ff718d2d182af4639870dc6e4247f684d81a8b2dc2649f8517b9fc53\/work\"\n }\n },\n\u2026<\/pre>\n$ podman info\n\u2026\nOCIRuntime:\n package: runc-1.0.0-54.rc5.dev.git2abd837.module+el8+2769+577ad176.x86_64\n path: \/usr\/bin\/runc\n version: 'runc version spec: 1.0.0'\n\u2026\nstore:\n ConfigFile: \/home\/clustadmin\/.config\/containers\/storage.conf\n ContainerStore:\n number: 0\n GraphDriverName: overlay<\/pre>\n
$ sudo podman run -d -e 'ACCEPT_EULA=Y' -e \\\n> 'MSSQL_SA_PASSWORD=Password1' \\\n> --name 'sqltest' \\\n> -p 1460:1433 \\\n> -v \/var\/mssql\/data:\/var\/opt\/mssql\/data:Z \\\n> mcr.microsoft.com\/mssql\/rhel\/server:2019-CTP3.1\n4f5128d36e44b1f55d23e38cbf8819041f84592008d0ebb2b24ff59065314aa4\n$ sudo podman ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n4f5128d36e44 mcr.microsoft.com\/mssql\/rhel\/server:2019-CTP3.1 \/opt\/mssql\/bin\/sq... 4 seconds ago Up 3 seconds ago 0.0.0.0:1460->1433\/tcp sqltest<\/pre>\n
$ pstree\nsystemd\u2500\u252c\u2500NetworkManager\u2500\u2500\u25002*[{NetworkManager}]\n \u251c\u2500\u2026\n \u251c\u2500conmon\u2500\u252c\u2500sqlservr\u2500\u252c\u2500sqlservr\u2500\u2500\u2500138*[{sqlservr}]\n \u2502 \u2502 \u2514\u2500{sqlservr}<\/pre>\n$ sudo runc list -q\n4f5128d36e44b1f55d23e38cbf8819041f84592008d0ebb2b24ff59065314aa4<\/pre>\n
$ sudo lsns \n\u2026\n4026532116 net 2 9449 root \/opt\/mssql\/bin\/sqlservr\n4026532187 mnt 2 9449 root \/opt\/mssql\/bin\/sqlservr\n4026532188 uts 2 9449 root \/opt\/mssql\/bin\/sqlservr\n4026532189 ipc 2 9449 root \/opt\/mssql\/bin\/sqlservr\n4026532190 pid 2 9449 root \/opt\/mssql\/bin\/sqlservr\n\n$ ps aux | grep sqlservr\nroot 9449 0.1 0.6 152072 25336 ? Ssl 05:08 0:00 \/opt\/mssql\/bin\/sqlservr\nroot 9465 5.9 18.9 9012096 724648 ? Sl 05:08 0:20 \/opt\/mssql\/bin\/sqlservr\nclustad+ 9712 0.0 0.0 12112 1064 pts\/0 S+ 05:14 0:00 grep --color=auto sqlservr<\/pre>\n
sudo nsenter -t 17182 --mount --uts --ipc --net --pid sh\nsh-4.2# ps aux\nUSER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND\nroot 1 0.0 0.7 152076 28044 ? Ssl Jul23 0:00 \/opt\/mssql\/bin\/sqlservr\nroot 9 2.2 19.7 9034224 754820 ? Sl Jul23 0:28 \/opt\/mssql\/bin\/sqlservr\nroot 319 0.0 0.0 13908 3400 ? S 00:01 0:00 sh\nroot 326 0.0 0.1 53832 3900 ? R+ 00:02 0:00 ps aux<\/pre>\n
$ ls -l\ntotal 40\ndrwxrwxr-x. 2 clustadmin clustadmin 70 Jul 24 02:06 BestPractices\ndrwxrwxr-x. 2 clustadmin clustadmin 80 Jul 24 02:06 DMK\n-rw-rw-r--. 1 clustadmin clustadmin 614 Jul 24 02:06 docker-compose.yml\n-rw-rw-r--. 1 clustadmin clustadmin 2509 Jul 24 02:06 Dockerfile\n-rw-rw-r--. 1 clustadmin clustadmin 3723 Jul 24 02:06 entrypoint.sh\n-rw-rw-r--. 1 clustadmin clustadmin 1364 Jul 24 02:06 example.docker-swarm-compose.yml\n-rw-rw-r--. 1 clustadmin clustadmin 504 Jul 24 02:06 healthcheck.sh\n-rw-rw-r--. 1 clustadmin clustadmin 86 Jul 24 02:06 mssql.conf\n-rw-rw-r--. 1 clustadmin clustadmin 4497 Jul 24 02:06 postconfig.sh\n-rw-rw-r--. 1 clustadmin clustadmin 2528 Jul 24 02:06 Readme.md\ndrwxrwxr-x. 2 clustadmin clustadmin 92 Jul 24 02:06 scripts<\/pre>\n
$ sudo podman build -t dbi_mssql_linux:2019-CTP3.1 .\n\u2026\n--> 5db120fba51f3adc7482ec7a9fed5cc4194f13e97b855d9439a1386096797c39\nSTEP 65: FROM 5db120fba51f3adc7482ec7a9fed5cc4194f13e97b855d9439a1386096797c39\nSTEP 66: EXPOSE ${MSSQL_TCP_PORT}\n--> 8b5e8234af47adb26f80d64abe46715637bd48290b4a6d7711ddf55c393cd5a8\nSTEP 67: FROM 8b5e8234af47adb26f80d64abe46715637bd48290b4a6d7711ddf55c393cd5a8\nSTEP 68: ENTRYPOINT [\"\/usr\/local\/bin\/entrypoint.sh\"]\n--> 11045806b8af7cf2f67e5a279692e6c9e25212105bcd104ed17b235cdaea97fe\nSTEP 69: FROM 11045806b8af7cf2f67e5a279692e6c9e25212105bcd104ed17b235cdaea97fe\nSTEP 70: CMD [\"tail -f \/dev\/null\"]\n--> bcb8c26d503010eb3e5d72da4b8065aa76aff5d35fac4d7958324ac3d97d5489\nSTEP 71: FROM bcb8c26d503010eb3e5d72da4b8065aa76aff5d35fac4d7958324ac3d97d5489\nSTEP 72: HEALTHCHECK --interval=15s CMD [ \"\/usr\/local\/bin\/healthcheck.sh\" ]\n--> e7eedf0576f73c95b19adf51c49459b00449da497cf7ae417e597dd39a9e4c8f\nSTEP 73: COMMIT dbi_mssql_linux:2019-CTP3.1<\/pre>\n$ sudo podman images\nREPOSITORY TAG IMAGE ID CREATED SIZE\nlocalhost\/dbi_mssql_linux 2019-CTP3.1 e7eedf0576f7 2 minutes ago 1.79 GB\nmcr.microsoft.com\/mssql\/rhel\/server 2019-CTP3.1 dbba412361d7 3 weeks ago 1.79 GB<\/pre>\n
$ sudo podman run -d -e 'ACCEPT_EULA=Y' \\\n> -e 'MSSQL_SA_PASSWORD=Password1' -e 'DMK=Y' \\\n> --name 'sqltest2' \\\n> -p 1470:1433 \\\n> localhost\/dbi_mssql_linux:2019-CTP3.1\nd057e0ca41f08a948de4206e9aa07b53450c2830590f2429e50458681d230f6b<\/pre>\n
$ sudo podman exec -ti d057 \/opt\/mssql-tools\/bin\/sqlcmd -S localhost -U sa -P Password1 -Q\"SELECT name from sys.databases\"\nname\n--------------------------------------------------------------------------------------------------------------------------------\nmaster\ntempdb\nmodel\nmsdb\ndbi_tools<\/pre>\n
$ sudo podman run -d -e 'ACCEPT_EULA=Y' -e \\\n'MSSQL_SA_PASSWORD=Password1' \\\n--name 'sqltestwithnovolumes' \\\n-p 1480:1433 \\\nmcr.microsoft.com\/mssql\/rhel\/server:2019-CTP3.1\n7e99581eaec4c91d7c13af4525bfb3805d5b56e675fdb53d0061c231294cd442<\/pre>\n
$ sudo podman generate kube -s 7e99\n# Generation of Kubernetes YAML is still under development!\n#\n# Save the output of this file and use kubectl create -f to import\n# it into Kubernetes.\n#\n# Created with podman-1.0.2-dev\napiVersion: v1\nkind: Pod\nmetadata:\n creationTimestamp: 2019-07-24T03:52:18Z\n labels:\n app: sqltestwithnovolumes\n name: sqltestwithnovolumes\nspec:\n containers:\n - command:\n - \/opt\/mssql\/bin\/sqlservr\n env:\n - name: PATH\n value: \/usr\/local\/sbin:\/usr\/local\/bin:\/usr\/sbin:\/usr\/bin:\/sbin:\/bin\n - name: TERM\n value: xterm\n - name: HOSTNAME\n - name: container\n value: oci\n - name: ACCEPT_EULA\n value: \"Y\"\n - name: MSSQL_SA_PASSWORD\n value: Password1\n image: mcr.microsoft.com\/mssql\/rhel\/server:2019-CTP3.1\n name: sqltestwithnovolumes\n ports:\n - containerPort: 1433\n hostPort: 1480\n protocol: TCP\n resources: {}\n securityContext:\n allowPrivilegeEscalation: true\n capabilities: {}\n privileged: false\n readOnlyRootFilesystem: false\n workingDir: \/\nstatus: {}\n---\napiVersion: v1\nkind: Service\nmetadata:\n creationTimestamp: 2019-07-24T03:52:18Z\n labels:\n app: sqltestwithnovolumes\n name: sqltestwithnovolumes\nspec:\n ports:\n - name: \"1433\"\n nodePort: 30309\n port: 1433\n protocol: TCP\n targetPort: 0\n selector:\n app: sqltestwithnovolumes\n type: NodePort\nstatus:\n loadBalancer: {}<\/pre>\n