[Qt-creator] More issues with QtCreator using dockers

[Jochen Becher]

Hi Marcus,

thank you for your quick response. I will merge my two dockerfiles into one and create a ticket for the long name issue.

Regards, Jochen


Am Freitag, dem 10.10.2025 um 08:20 +0000 schrieb Marcus Tillmanns:
> Hi Jochen,
> 
> 
> 
> 
> > 
> > 1. You can select different docker devices for build and run. But the debugger is always taken from the build docker. One cannot even
> > select
> > a debugger from the run device manually. This is a blocker as the build device cannot run the application (that's the reason why you
> > have a
> > separate run device and docker image).
> 
> We currently (and historically) assume that:
> * For docker: You can run and build on the same device
> * For ssh run device: You cannot debug directly on the run device, but need the debugger to come from the build device
> 
> There is no provision for “dual docker device” setups at the moment.
> 
> > 
> > 
> > 2. The default name of the kit is %{Device:Name}. The Device:Name is taken from the Run device which surprises me because the build
> > device
> > is surely more important, isn't it?
> 
> This is historical, since in the beginning there was only the Run device, while building would happen locally. It might make sense to put
> both information into the default name these days.
> 
> > 
> > 
> > 3. Qt Version, Compilers and Debuggers are all named after the docker image name, tag, id and some extra text. At least in my case the
> > docker image names are build from the docker registry (some artifactory name), some folders to structure the dockers and the tag (which
> > is
> > pretty long as it lists several component versions used in the image). At the end the strings are something like 160 characters long
> > which
> > is an issue in the UI.
> 
> Maybe open a ticket with some screenshots of the particular issues.
> 
> > 
> > 4. Detected debuggers are never removed automatically and cannot be removed manually. While Qt versions and compilers are removed
> > automatically when the device is deleted, the detected debuggers stay and the list grows longer and longer over time.
> 
> This should be fixed in Qt Creator 18.0.
> 
> > 
> > All in all there are far too many steps needed to get a clean device and kit set up to build and run and application using docker. The
> > new
> > concept with the json description in QtC 18 seems like a good way to go. Does this solve some of the issues (like the naming or
> > selection of
> > the debugger)?
> 
> No, this does not change the way debuggers are chosen.
> 
> Please feel free to open Tickets for the issues plaguing you. You could also try the Qt Creator 18 rc1 snapshots
> (https://download.qt.io/snapshots/qtcreator/18.0/18.0.0-rc1/)
> 
> Cheers,
> Marcus
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20251010/ae61e3a1/attachment.htm>