Podman does not refresh when container started

Ask Fedora
,
1

Since upgrade:

Upgrade  containerd.io-0:2.1.5-1.fc42.x86_64                               User            docker-ce-stable
  Upgrade  docker-ce-3:29.0.0-1.fc42.x86_64                                  User            docker-ce-stable
  Upgrade  docker-ce-cli-1:29.0.0-1.fc42.x86_64                              User            docker-ce-stable
  Upgrade  docker-ce-rootless-extras-0:29.0.0-1.fc42.x86_64                  Weak Dependency docker-ce-stable
  Replaced docker-ce-3:28.5.2-1.fc42.x86_64                                  User            @System
  Replaced docker-ce-cli-1:28.5.2-1.fc42.x86_64                              User            @System
  Replaced docker-ce-rootless-extras-0:28.5.2-1.fc42.x86_64                  Weak Dependency @System
```

Can’t run terminal until podman Desktop is stopped and restarted.

podman version 5.6.2

Docker version 29.0.2, build 8108357

2

Running containers via docker and podman at the same time can cause issues and unexpected behavior. I would suggest using only one of the two, preferably podman.

3

Good point - I started with docker so I don’t use pods. However, the containers were created using the Podman Desktop. Used Podman Desktop to create ‘my first pod’ and removed several times and it locked up Fedora. Had to reboot. Is there a reason to use pods when not using k8’s?

4

Works in my machines. Are you sure the locked up system was connected to Podman and not just a weird coincidence?

In my experience, Podman is really stable and I prefer it over the Docker stack.

I use pods when I want to run multiple containers together, say an application, its database, and Redis/Valkey. For a single container, you don’t need a pod.

5

Upgraded to f43, same problem. Created pod with following but the app can’t find the container(port):

podman pod create -n mssql-pod -p 0.0.0.0:1433:1433
podman create -t --pod mssql-pod --name mssql_server mcr.microsoft.com/mssql/server:2022-latest

With just using image/container that works I get RUNNING PORTS 1433,1433 with the pod I get

RUNNING PORT 1433 . As for the locking up Fedora, when deleting a pod at times the desktop does take over the system but eventually releases it.

I should mention that the pod indicates RUNNING but it doesn’t really start the sqlserver image.

6

Which app cannot find the port?

When trying your commands, I end up with the error that the server requires accepting of the EULA before starting. So … it doesn’t start, I guess, which matches what podman ps shows.

~ ❯ podman pod create -n mssql-pod -p 127.0.0.1:1433:1433
8178cb5c1afb554fcd3afb7a5b4cd140913a06678fbf84581a736d5b6f9ffd94

~ ❯ podman create -t --pod mssql-pod --name mssql_server mcr.microsoft.com/mssql/server:2022-latest
Trying to pull mcr.microsoft.com/mssql/server:2022-latest...
Getting image source signatures
Copying blob 95d90ad22b86 done   | 
Copying blob 4e1957cbf2ff done   | 
Copying blob 6420ce242662 done   | 
Copying config a2fbff3215 done   | 
Writing manifest to image destination
03d0397f09bc416eb6e995d148c2788709fe5bcc6248b72aa7ff3c21711ad9cf

~ ❯ podman pod start mssql-pod
mssql-pod

~ ❯ podman ps
CONTAINER ID  IMAGE                            COMMAND     CREATED             STATUS                 PORTS                                      NAMES
216813f1ffec                                               About a minute ago  Up 5 seconds           127.0.0.1:1433->1433/tcp                   8178cb5c1afb-infra

~ ❯ podman logs mssql_server
SQL Server 2022 will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
The SQL Server End-User License Agreement (EULA) must be accepted before SQL
Server can start. The license terms for this product can be downloaded from
http://go.microsoft.com/fwlink/?LinkId=746388.

You can accept the EULA by specifying the --accept-eula command line option,
setting the ACCEPT_EULA environment variable, or using the mssql-conf tool.

Pods have a separate running state. They can exit when all containers exited, see --exit-policy in podman-pod-create. Are you sure that there wasn’t an error for the mssql container and it exited, like I see on my system?

7

Yes the mssql container was status exit. I added -i fedora bash and the pod was running green but I didn’t see the mssql container. App still failed. I’ll try the Eula.

8

This works:

podman pod create -n mssql-pod -p 0.0.0.0:1460:1433
podman create  -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=Passw0rd'  --name mssql_server  mcr.microsoft.com/mssql/server:2022-latest
2 Likes
9

Glad you figured out your issue.