| jovial` | Any appetite for getting a more complete rocky-container image build? Currently it lacks basic tools like passwd. We could either flesh out the current dockerfile or add a new one that you choose with DIB_RELEASE/DIB_CONTAINER_FILE. | 09:00 |
|---|---|---|
| jovial` | On second thoughts, maybe the container file isn't the best thing to modify as we won't have stuff like DIB_DISTIRUBTION_MIRROR configured in there, right? | 09:06 |
| clarkb | jovial`: in the past I think we've been happy to let the minimal installs be minimal. In opendev we have an element called infra-package-needs to layer in extra packages to supplement the minimal install | 14:10 |
| clarkb | that said passwd is probably something worth adding | 14:11 |
| clarkb | and yes the dockerfile may not be the best place to do that. Adding it as a normal package dep to the element should bring in support for the other bits | 14:12 |
| opendevreview | Will Szumski proposed openstack/diskimage-builder master: Adds rocky-container-generic https://review.opendev.org/c/openstack/diskimage-builder/+/855521 | 14:44 |
| jovial` | Thanks clarkb. Just seen these messages. I'll make a patch to passwd to the minimal image. Maybe we could consider installing the @core package group. | 14:48 |
| opendevreview | Will Szumski proposed openstack/diskimage-builder master: Adds passwd to rocky-container os packages https://review.opendev.org/c/openstack/diskimage-builder/+/855530 | 15:30 |
| clarkb | jovial`: using a new element like that seems like a good approach. Backward compatible without adding extra stuff to existing users and more fully featured for people that need it | 15:32 |
| clarkb | personally I think the cloud-init user being distro specific is a massive anti pattern we should all move away from, but as long as the distros do it I guess we don't have much choice | 15:33 |
| jovial` | Thanks for taking a look. Agreed that setting the cloud-user is a bit on anti-pattern. My thinking was that alot of people start out with the generic cloud image and switch to using DIB when they want to do some customisation. Keeping the cloud-user consistent with the generic cloud image would be the least surprising option in that scenario. Happy to take that out though. | 16:10 |
| clarkb | jovial`: another thought, I think dib has a cloud-init element. Would it make sense to leave cloud-init out of this new element entirely and expect dib users to use the cloud-init element instead? | 16:42 |
| jovial` | Was thinking it would be batteries included and that cloud-init is pretty essential. Maybe we could add the cloud-init element as a dependency instead? | 17:04 |
| clarkb | jovial`: well some of us don't use cloud-init | 17:10 |
| clarkb | But those users could start with the minimal element I guess | 17:10 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!