[Help] [Migrate to Podman from Docker] [how to !!!!]

[pan102887]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

• Task: Migrate it from Docker to podman
• Problem: The project Incompatible with podman. it can not start up via replase the "docker compose" to "podman-compose"
• Why Do This: For some reasons, I can not use Docker but PodMan
• looking For: Answers to "Should I do this?" and "How to? (What I need to do?)"

2. Additional context or comments

WARNING:podman_compose:WARNING: unused networks: milvus,opensearch-net
Error: no container with name or ID "docker_nginx_1" found: no such container
Error: no container with name or ID "docker_worker_beat_1" found: no such container
Error: no container with name or ID "docker_worker_1" found: no such container
Error: no container with name or ID "docker_api_1" found: no such container
Error: no container with name or ID "docker_ssrf_proxy_1" found: no such container
Error: no container with name or ID "docker_plugin_daemon_1" found: no such container
Error: no container with name or ID "docker_redis_1" found: no such container
Error: no container with name or ID "docker_sandbox_1" found: no such container
Error: no container with name or ID "docker_web_1" found: no such container
docker_init_permissions_1
Error: no container with ID or name "docker_nginx_1" found: no such container
Error: no container with ID or name "docker_worker_beat_1" found: no such container
Error: no container with ID or name "docker_worker_1" found: no such container
Error: no container with ID or name "docker_api_1" found: no such container
Error: no container with ID or name "docker_plugin_daemon_1" found: no such container
Error: no container with ID or name "docker_ssrf_proxy_1" found: no such container
Error: no container with ID or name "docker_sandbox_1" found: no such container
Error: no container with ID or name "docker_redis_1" found: no such container
Error: no container with ID or name "docker_web_1" found: no such container
docker_init_permissions_1
7b46cb7669077d4d1588470430dfbe918bb3bba29bc99682af69851519f798b1
docker_default
docker_ssrf_proxy_network
58011acb8b079756e4350626a6387312066f7befcc9bd5ee7b591d6e272d8c08
3d3b48dfb33c6f2387941193ee91e3e057fa6bb2cee585a08d83c5c176db7708
633cdb26afd883dd8a942967c4d07979d2cb60e21064cd2f1652a7c37bbf9e92
b5e17012c5623cfbf8b0bcb3b4a3249acb178bf4f3783a05ec306bf7819884a5
0a0fa35b73f90589ef8b83dc8acf6a126316ad118875eb4849f23f41372ec627
540fc0eb5ab70b18f12a2ed714dcd58d4cb1480d626732a01381c87470c840c4
b8252f53a35399bfb300d69e81e93c238b77124699ae04cbc0a34d75b32017f7
8f4ebac3dd6d3278328e64cb472cbd948eeb1a3ecc9e6f5977445ea39c060588
8a8f84c1b901d2705852818967d03398969ec79275544d64a7fdaaf27a3e0840
0ca2be5bbe5247f24f014c1797a143f6bb345dcd934d325a4b59391ab19e9343
843898928d43be99f7a3becc2c3a6d26b36aa0cb93a950219dc40b971eac2dff
docker_init_permissions_1
docker_web_1
docker_redis_1
docker_sandbox_1
docker_ssrf_proxy_1
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\XPENG_USER\AppData\Roaming\Python\Python313\Scripts\podman-compose.exe\__main__.py", line 6, in <module>
    sys.exit(main())
             ~~~~^^
  File "C:\Users\XPENG_USER\AppData\Roaming\Python\Python313\site-packages\podman_compose.py", line 4256, in main
    asyncio.run(async_main())
    ~~~~~~~~~~~^^^^^^^^^^^^^^
  File "C:\Python313\Lib\asyncio\runners.py", line 195, in run
    return runner.run(main)
           ~~~~~~~~~~^^^^^^
  File "C:\Python313\Lib\asyncio\runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "C:\Python313\Lib\asyncio\base_events.py", line 725, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "C:\Users\XPENG_USER\AppData\Roaming\Python\Python313\site-packages\podman_compose.py", line 4252, in async_main
    await podman_compose.run()
  File "C:\Users\XPENG_USER\AppData\Roaming\Python\Python313\site-packages\podman_compose.py", line 2072, in run
    retcode = await cmd(self, args)
              ^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\XPENG_USER\AppData\Roaming\Python\Python313\site-packages\podman_compose.py", line 3188, in compose_up
    exit_code = await run_container(
                ^^^^^^^^^^^^^^^^^^^^
        compose, cnt["name"], deps_from_container(args, cnt), ([], "start", [cnt["name"]])
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "C:\Users\XPENG_USER\AppData\Roaming\Python\Python313\site-packages\podman_compose.py", line 3089, in run_container
    await check_dep_conditions(compose, deps)
  File "C:\Users\XPENG_USER\AppData\Roaming\Python\Python313\site-packages\podman_compose.py", line 3053, in check_dep_conditions
    deps_cd.extend(compose.container_names_by_service[d.name])
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'db_mysql'

[dosubot[bot]]

Hi @pan102887! I'm Dosu and I’m helping the dify team.

Migrating Dify from Docker Compose to Podman Compose is not straightforward and is likely to be problematic due to several compatibility issues:

• Dify's docker-compose.yaml uses Docker Compose v2 features like depends_on with condition keys (such as service_healthy and service_completed_successfully), which Podman Compose does not fully support. This leads to dependency resolution errors like the KeyError for 'db_mysql' because Podman Compose may not instantiate profile-scoped services unless explicitly enabled, and it doesn't handle these conditions the same way as Docker Compose does. As a result, services like db_mysql may not be started, causing failures in dependent services and errors during startup.
• Container naming conventions differ between Docker Compose and Podman Compose. Podman Compose may not generate container names like docker_nginx_1, leading to "no container with name or ID ..." errors when services try to reference each other by these names.
• Network and profile handling also differ, resulting in warnings about unused networks and potentially missing service connectivity.
• Recent changes in Dify (such as the introduction of an init_permissions container to fix storage permissions) rely on these Compose features and further complicate compatibility with Podman Compose, which does not support all dependency conditions or startup order guarantees required by Dify's setup.

If you must use Podman, you would need to manually adjust the compose files: remove or rewrite depends_on conditions, explicitly enable all required profiles, and ensure container names and networks are compatible with Podman Compose's behavior. However, this is non-trivial and may require ongoing maintenance as Dify evolves.

At this time, running Dify with Podman Compose is not recommended unless you are comfortable with significant manual intervention and troubleshooting.
Reference: docker-compose.yaml analysis

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}