Do not create user `almamgr` in our image

[dneise]

I would like to avoid creating the user almamgr in our image. I think user creation should be up the the end-user of our image.

So I would like to remove this:

ACS-Docker-Image/Dockerfile

Lines 117 to 124 in 9df3cbd

	# Here we create the user almamgr
	RUN groupadd -g 1000 almamgr && \
	useradd -g 1000 -u 1000 -d /home/almamgr -m -s /bin/bash almamgr && \
	passwd -d almamgr && \
	# For conveniece we source the alma .bash_profile.acs in the user .bash_rc
	# and export JAVA_HOME
	echo "source /alma/ACS-2020AUG/ACSSW/config/.acs/.bash_profile.acs" >> /home/almamgr/.bashrc && \
	echo "export JAVA_HOME=$JAVA_HOME" >> /home/almamgr/.bashrc

Reasons:

• not everybody might want a user named almamgr
• c.f. creation of user "almamgr" with UID = 1000 ? #23 no everybody might want the user to have UID = 1000
• I think it is not needed (I have to check this and provve it to you of course) and what is not needed, should maybe not be in here.

[dneise]

Oh my god .. I just realized I had a bad typo in the title of this issue ... sorry about that.

[emiliogq]

I like this, but I don't know if ACS currently allow us to do so.

May be we can ask in slack- What do you think?

[dneise]

Ah .. so you mean ALMA people want always the almamgr user? So this docker image must contain that user?
That is possible...

We can ask in the Slack, sure. But first I want to find the time to make a proposal.
And show how it behaves without the almamgr user... maybe I make even a short video or so.

Then we can discuss about a specific proposal. Should make discussions easier

[emiliogq]

I applied the changes in 5d3cbbe

Take a look if you want

@tstaig (in #docker-image slack channel) :

Regarding almamgr user... a simple image can remove it altogether, as you state, everything will work correctly with root
The reason I have a specific user is because I usually mount some paths (repositories, data dir, etc.), and I don't like that they get written as root on my host filesystem
But that is, as you say, a more advanced use case