Resolve "ALICE eos-docker update to EOS 4.1.31"

Closes #2 (closed)

added 1 commit

• d2a85f5f - Improved eos docker versions

Compare with previous version

@esindril While solving problem in https://its.cern.ch/jira/browse/EOS-2024 , you said that it was not forseen to run eos service from docker container. I am doing it that way. Is there any security issue or problem to do it that way?

It's not that it was not foreseen, it's that for example a few months ago one was not able to start a service inside a container using systemd. It was possible but with some hacks. One needed either systemd running inside the container or the host systemd exposed to the services inside the container.

With old style SysV scripts this is not an issue since the service script just runs the /etc/rc.d/../eos scripts and this works just fine.

As you can see here for example: https://gitlab.cern.ch/eos/eos-docker/blob/master/image_scripts/eos_mgm_setup.sh#L6

The way we start the daemon(s) inside these containers is just by running the executable and not by using the service command. The service command might not be available in the current container image, think Fedora. Therefore, in this case one has to take all the necessary steps to ensure the directories that EOS expects are created and have the proper permissions.

We do all the preparations here: https://gitlab.cern.ch/eos/eos-docker/blob/master/image_scripts/eos_setup.sh#L18

If it all works for you, then there is no problem.

Thanks for answer. There is no problem to run it. I am running currently one ALICE EOS instance in Kosice. Using https://gitlab.cern.ch/eos/eos-docker/blob/master/projects/alice/Dockerfile.base and https://gitlab.cern.ch/eos/eos-docker/blob/master/projects/alice/Dockerfile.alice

Now you can merge this. I improved some versioning of docker image using build script

unmarked as a Work In Progress

assigned to @esindril

merged

mentioned in commit a328ff9d