search

OSC / ood-images

14 stars 8 forks source link

remove podman stack #10

Closed johrstrom closed 3 years ago

johrstrom commented 4 years ago

I'm going to remove the podman stack becuase really we don't need it.

Essentially the use case for me was to map myself to a user inside the container. After getting a lot of mileage out the podman images I found that I could do the same thing with the Docker image we simply enable these 2 things inside the container.

The idea is this: $(id -u) (whoever you are) starts the image and maps to ood (uid 1000 inside the container). So ood needs sudo privileges to start httpd.

I had to remove the passwords because of tty problems, though I'm looking for a way around that now. But mounting the /etc/sudoers.d/ood file as $(id -u) is giving me problems.

johrstrom commented 4 years ago

I don't really need this anymore and really, it's probably confusing to have two container stacks.

treydock commented 4 years ago

FWIW if you need to do UID changing , look at build.sh in ondemand-packaging repo. I stole some wrapper ideas from passenger RPM build workflow that changes the ood user UID/GID inside the container to match UID/GID of person running docker so that files written in the container to a RW volume are accessible outside the container.

johrstrom commented 3 years ago

There's no need for this given the rake tasks that now build containers.