AlmaLinux 8.10
Current Version: 2.3
Build: 6
Current Commit: bd353150b20020946036cda8eb82545f09269914

After upgrading to 2.3.6 I’m not able to Create a new container via CyberPanel.
Whenever I’m accessing Docker Manager - Create new container I get “The requested resource was not found on this server”.
Everything else in Docker Manger (pulling images/visiting Running containers) seems to work properly. Manage containers shows all previous created containers and their details.

[root@cp1 ~]# dnf list installed|grep docker
containerd.io.x86_64 1.6.32-3.1.el8 @docker-ce-stable
docker-buildx-plugin.x86_64 0.14.0-1.el8 @docker-ce-stable
docker-ce.x86_64 3:26.1.3-1.el8 @docker-ce-stable
docker-ce-cli.x86_64 1:26.1.3-1.el8 @docker-ce-stable
docker-ce-rootless-extras.x86_64 26.1.3-1.el8 @docker-ce-stable
docker-compose-plugin.x86_64 2.27.0-1.el8 @docker-ce-stable

Page not found (404)

Using the URLconf defined in CyberCP.urls, Django tried these URL patterns, in this order:

1. base/
2. [name=‘adminLogin’]
3. verifyLogin [name=‘verifyLogin’]
4. logout [name=‘logout’]
5. packages/
6. websites/
7. tuning/
8. ftp/
9. serverstatus/
10. dns/
11. users/
12. dataBases/
13. email/
14. serverlogs/
15. firewall/
16. backup/
17. managephp/
18. manageSSL/
19. api/
20. filemanager/
21. emailPremium/
22. manageservices/
23. plugins/
24. emailMarketing/
25. cloudAPI/
26. docker/ ^$ [name=‘dockerHome’]
27. docker/ ^getTags$ [name=‘getTags’]
28. docker/ ^runContainer$ [name=‘runContainer’]
29. docker/ ^submitContainerCreation$ [name=‘submitContainerCreation’]
30. docker/ ^listContainers$ [name=‘listContainers’]
31. docker/ ^getContainerList$ [name=‘getContainerList’]
32. docker/ ^getContainerLogs$ [name=‘getContainerLogs’]
33. docker/ ^installImage$ [name=‘installImage’]
34. docker/ ^delContainer$ [name=‘delContainer’]
35. docker/ ^doContainerAction$ [name=‘doContainerAction’]
36. docker/ ^getContainerStatus$ [name=‘getContainerStatus’]
37. docker/ ^exportContainer$ [name=‘exportContainer’]
38. docker/ ^saveContainerSettings$ [name=‘saveContainerSettings’]
39. docker/ ^getContainerTop$ [name=‘getContainerTop’]
40. docker/ ^assignContainer$ [name=‘assignContainer’]
41. docker/ ^searchImage$ [name=‘searchImage’]
42. docker/ ^manageImages$ [name=‘manageImages’]
43. docker/ ^getImageHistory$ [name=‘getImageHistory’]
44. docker/ ^removeImage$ [name=‘removeImage’]
45. docker/ ^recreateContainer$ [name=‘recreateContainer’]
46. docker/ ^installDocker$ [name=‘installDocker’]
47. docker/ ^images$ [name=‘containerImage’]
48. docker/ ^view/(?P.+)$ [name=‘viewContainer’]
49. docker/ manage/int:dockerapp/app [name=‘Dockersitehome’]
50. docker/ getDockersiteList [name=‘getDockersiteList’]
51. docker/ getContainerAppinfo [name=‘getContainerAppinfo’]
52. docker/ getContainerApplog [name=‘getContainerApplog’]
53. docker/ recreateappcontainer [name=‘recreateappcontainer’]
54. docker/ RestartContainerAPP [name=‘RestartContainerAPP’]
55. docker/ StopContainerAPP [name=‘StopContainerAPP’]
56. container/
57. CloudLinux/
58. IncrementalBackups/

The current path, docker/runContainer/, didn’t match any of these.

You have the same issue as i have on one server.
Almalinux 9 - CyberPanel Project / Feature Request - CyberPanel Community

Yes. The current path, docker/runContainer/, didn’t match any of these.
As far as I saw you are on AlmaLinux 9, while I’m still on 8.
It used to work prior upgrading to 2.3.6.
It is not a docker issue, because I see the containers running under “Manage Containers” and also if I’m stating a container from command prompt it is shown there as Unlisted Container.

image1258×723 41.2 KB

@ sajetek_developer
Your solution: Almalinux 9 - #55 by sajetek_developer worked also for me. Thank you.

@Master3395 Thank you for pinpointing your similar issue.