Configure pkg repo to be used in jails

[urosgruber]

I'm not sure if this is possible or if it ok to change host pkg.conf would work, but I would like to use our internal repo instead of freebsd repo. Maybe some config attribute would be nice.

[igalic]

per jail, or globally?

[gronke]

This is currently done by the Pkg class. A local pkg config folder is created per Release and used for the local pkg commands. Because the pkg source has to fit the jails release, this all is stored in a Release-like structure in /iocage/pkg/<RELEASE>/.... Packages can be fetched, installed to a jail or both. The class will take care of the read-only NullFS mountpoint of the mirror data on the first run.

[urosgruber]

I think for now globally would be ok or per release. Per jail might be overkill. @gronke so I can safely update config to fit my needs?

[igalic]

@gronke this needs better documentation then

[gronke]

I think for now globally would be ok or per release. Per jail might be overkill.

It is implemented per release, so that the userland matches the installed packages.

@gronke so I can safely update config to fit my needs?

Of course you can add your own package sources within the jail - libiocage will not change existing ones. Or do you intend to install packages from a custom source?

[urosgruber]

@gronke we always use custom source (internal build server).

[gronke]

Got you! It is not configurable yet, but there should be a way to work with a custom build server. I haven't entirely figured out how this integrates with different releases and how some jails can install from a custom remote while others don't.

[igalic]

how about a pkg.* setting ;)

[igalic]

so, today i tried to rebuild a host, hit a fun issue: where a package was removed from latest but the documented alternative was not provided there.

so, i'd like this, too, very much…
the package still exists in quarterly, but our Pkg uses latest