ciq sdk 3.2.3 and docker

Hi,

did anyone manage to use ciq SDK 3.2.3 inside docker?

Even after copying the ~/.Garmin folder from my local installation to the container the build is still complaining about not being able to find the devices ...

jim_m_58 over 6 years ago

Did this work with the 3.2.1 and 3.2.2 SDK?

The path to devices and fonts is fixed. It's not relative to the SDK. If you run the sdk manager in your docker image, it will put those where the SDK expects them.

Tobi over 6 years ago in reply to jim_m_58

I did not try any other 3.2.X but directly switched from 3.1.9.

I tried to keep the same path to the SDK in the container as it is on the machine i copied the SDK data from but there seems to be something else missing...

The idea behind the docker image is to be able to build on a (headless) jenkins server so unless there is a "no GUI" way of running the sdkmanager this is not really an option :-(

jim_m_58 over 6 years ago in reply to Tobi

Starting with 3.2, devices and fonts are split from the SDK. While the sdk can be anywhere, devices and fonts must be in a specific location.

On windows, that's c:\users\(you)\appdata\roaming\garmin\connectiq

I'm not sure what that path is on your setup.

Tobi over 6 years ago in reply to jim_m_58

Path for Linux is ~/.Garmin/ConnectIQ.

maybe i need to keep the path and the user - so far i only tried copying the files to my build users home folder or keeping the or keeping path (so in another users home folder form the build users POV)

jim_m_58 over 6 years ago in reply to Tobi

Could be an env variable is involved. My only linux like system is a pi, so I can't check.

Tobi over 6 years ago in reply to jim_m_58

woohoo - turns out it works if i run the sdk manager as build user on the local machine to get the files and then copy it to the same place inside the container it works ;-)