search

RotherOSS / otobo

OTOBO is one of the most flexible web-based ticketing systems used for Customer Service, Help Desk, IT Service Management. https://otobo.io/
GNU General Public License v3.0
240 stars 72 forks source link

Hardcode /root/.cpanm in cleanup command in Dockerfile #3494

Closed bschmalhofer closed 3 hours ago

bschmalhofer commented 2 weeks ago

This issue was initially reported in the otobo-docker repository:

I now did some digging and found an old issue with a similar problem, see https://github.com/RotherOSS/otobo/issues/972 . The strange UIDs seem to stem from CPAN. This satisfies my concern that something very strange is going on.

The fix for the old problem was the cleaning up of $HOME/.cpanm . This solution still seems to be in place and seems to be working for most environments. In your environment however, the build context seems to be different. Maybe your $USER is / instead of /root.

I see no problems in hardcoding /root/.cpanm . I'll do that in a branch in the otobo repository.

Originally posted by @bschmalhofer in https://github.com/RotherOSS/otobo-docker/issues/136#issuecomment-2168145267

bschmalhofer commented 2 weeks ago

Hi @tb-killa,

could you take a look at the branch https://github.com/RotherOSS/otobo/tree/issue-%233494-cleanup_of_dot_cpanm ? Does the build work for you with the hard coded /root/.cpanm ?

Best regards, Bernhard

bschmalhofer commented 1 week ago

The same or a similar problem was reported in the OTOBO community forum; https://otobo.io/forums/topic/installation-von-otobo-otobolatest-11_0-failed-to-register-layer/

tb-killa commented 1 week ago

@bschmalhofer Kann bestätigen, läuft ohne Probleme durch :)

bschmalhofer commented 1 week ago

@tb-killa , I'm still confused about this issue. My current understanding is that your build of the Docker image worked because the build was done in the Docker LXC Container.

Anyways, I did another iteration on otobo.web.dockefile where I'm removing /root/.cpam in the RUN where cpanm is used. Could you try running with the devel Image rotheross/otobo:devel-rel-110 from Docker Hub? The image can be specified in the ,env_ file. Make sure that you call docker pull rotheross/otobo:devel-rel-11_0 before starting, so that you get the most recent build.

bschmalhofer commented 1 week ago

The last fixes in otobo.web.dockerfile are looking good. See https://otobo.io/forums/topic/installation-von-otobo-otobolatest-11_0-failed-to-register-layer/#post-31296 .

bschmalhofer commented 1 week ago

I checked whether the same problem is present in rel-10_0 and rel-10_1. These branches seem to be fine. The problem was introduced in #2278 for rel-11_0.

bschmalhofer commented 3 hours ago

No problems were encountered regarding the hard coded /root/.cpanm . Closing this issue.