#12369 Need CI container image with sudo enabled user
Closed: Upstream a month ago by kevin. Opened 2 months ago by abitrolly.

Describe what you would like us to do:


Official Fedora container image with a user inside. Basically:

FROM fedora:latest

# add `fedora` user to admin group and disable `sudo` password for it
RUN adduser fedora -G wheel \
  && echo "fedora       ALL=(ALL)       NOPASSWD: ALL" > /etc/sudoers.d/fedora

USER fedora

Asked here https://github.com/fedora-cloud/docker-brew-fedora/issues/118 but two weeks no decision.

Then here https://gitlab.com/fedora/infrastructure/konflux/infra-deployments/-/issues/8 no answers.

Finally @kevin here https://discussion.fedoraproject.org/t/enable-image-repository-on-gitlab/142905 gave me the pointer to this Pagure.

When do you need this to be done by? (YYYY/MM/DD)


Well, I would already use it for https://gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/4362


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: gitlab, medium-gain, medium-trouble

2 months ago

Hi. I directed you here from the discussion thread, but I don't think I understood what you were asking for.

I thought it was some infrastructure problem with the various repos... but that seems wrong.

If I now understand you, you would like this adjustment to the official fedora images we produce? Is that right?

I thought it was some infrastructure problem with the various repos... but that seems wrong.

Now there is also infrastructure problem with various repos, but in the end I just want updated image.

I am certain people will experience workflow disruption if instead of root they will have to deal with user, so I would provide a separate image, like fedora:41-ci.

What would this be for? What do you need a user inside of a default container image for?

So, the fedora base image is mostly managed by the Cloud SIG. I can't speak for if they would want to do this.

I hate to bounce you around yet again, but they can be located at https://pagure.io/cloud-sig (that has all the contact info).

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

a month ago

@kevin does Pagure allow to move the issue there? I am drained of carrying this horse body around.

@kevin nevermind. I copy/pasted the story here. https://pagure.io/cloud-sig/issue/437

Thanks for navigating me around. Although it is heavy, I am glad it is not dead yet. :sweat_smile:

Yeah, sorry for bouncing you around from place to place. Hopefully you can get a concrete answer there.

Maybe, but so far it looks like "works for me" answer.

Log in to comment on this ticket.

Metadata