I responded in the other topic. I leave the link here too for others: https://forums.docker.com/t/docker-webserver-cannot-be-reached/136608/10?u=rimelek
I am sorry, I didn’t mean that you are “just” familiar, by familiar I meant you are experienced, but even if someone has many years of experience in multiple kind of programming, containerization will still be new and a GUI will not be able to hide all the difficulties. It has a GUI to manage settings and discover images, containers and so on, but I don’t think it was ever the goal to be used by people who know nothing about containers. It just makes it a little easier to manage containers and start a new container, but not from compose (or not yet). Even the Dev Environment feature is still beta for a long time now.
I have heard that question from many people who heard about containers and tried the first time. Then they learned more about it and started it to make sense. It takes time. Forcing a project to run in a container without anyone in the team understanding it just because it is popular is wrong as much as allowing an employee to work on a project for a long time without proper documentation. Docker is powerful but it can powerfully “destroy” the project when it is developed and operated with the mindset of running softwares the traditional way. There is nothing wrong with running applications without containers if the developers and system administrators are not experienced Docker users. Using containers for the first time when there is not enough time to learn about that is really frustrating and gives you the impression as you had that Docker is basically useless and overcomplicated, although it is not the case. You just need someone to develop the Docker part or consult with you because even Docker experts will not neccesserily be expert in the required programming. Then if you have a Docker image that someone already created, and you get a yml file that was also created by someone else, you can basically copy and paste it and the application will most likely work because a container contains everything that the software required and you are not restrictied to use a specific Linux distribution on the host, because the container will contain that distribution and all you need is a compatible Linux kernel.
I don’t want to convince you about using Docker. It won’t help everyone, but in the long run, if you don’t have to do everything alone and you get proper documentation it can be extremely useful. Until that, if you have time to learn, you will need patiance, but if you don’t have time or just not interested in this yet, it is fully understandable if you go back to the well-known, stable way, if you can at the current stage of the project.
I myself had to realise recently that I was not enough for a specific solution in a project and it would have been irresponsible to stick with that when I took over the project so I chose another way that can be done easier by a single person.