Closed adlarkin closed 3 years ago
After taking a look at this comment from @gbiggs and looking a bit more into rocker and its extensions, I think that this setup can be simplified significantly by making use of the colcon extension and by writing my own ignition extension. I'll try going down that path to see how things go.
Essentially, my thought is to have users run a command like this:
rocker --ignition-<VERSION> --colcon --oyr-mount PATH/TO/COLCON/WORKSPACE -- image:tag
The --oyr-mount
is optional, but would point to a colcon workspace of ignition repositories and/or of a project that uses ignition on a user's system. Then, users can build the workspace inside of the container (if users don't use --oyr-mount
, they can omit the --colcon
argument as well).
I think that sounds eminently usable. Definitely the way to go.
This is meant to be used with https://github.com/ignition-tooling/gzdev/pull/23.
Take a look at the
README
for more information.