Bug 1859387

Summary: Container Review Request - php-73-fedora - Platform for building and running PHP 7.3 applications
Product: [Fedora] Fedora Container Images Reporter: cragr <craig>
Component: Container ReviewAssignee: Athos Ribeiro <athoscribeiro>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: athoscribeiro, clems.verna, container-review, fedoraproject
Target Milestone: ---Flags: athoscribeiro: fedora-review?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-18 17:12:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 177841    

Description cragr 2020-07-21 21:13:59 UTC
Container Build Info URL: https://github.com/sclorg/s2i-php-container/blob/master/7.3/Dockerfile.fedora
Description: PHP container image based on Fedora andintended for OKD and general usage, that provide a platform for building and running PHP applications.
Fedora Account System Username: cragr

Comment 1 cragr 2020-07-22 19:31:52 UTC
Maybe use a similar image naming scheme as the centos images like php-73-f31 for PHP version 7.3 Fedora version 31?

Comment 2 Athos Ribeiro 2020-07-27 21:04:21 UTC
Are you in the packager group already?

If not, you may also want to look for a sponsor.

See https://fedoraproject.org/wiki/Join_the_package_collection_maintainers

Comment 3 Athos Ribeiro 2020-07-27 21:14:58 UTC
Moreover, are you planning on packaging all those files in the directory with the Dockerfile?

Comment 4 cragr 2020-07-28 19:32:49 UTC
(In reply to Athos Ribeiro from comment #2)
> Are you in the packager group already?
> 
> If not, you may also want to look for a sponsor.
> 
> See https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
>
> Moreover, are you planning on packaging all those files in the directory with the Dockerfile?
>


I am not in the packager group and have contacted one person so far for sponsorship, status is pending.

I have no plans to package files, the image will be built using that exact Dockerfile.fedora from the sclorg repo.

Comment 5 Athos Ribeiro 2020-08-03 08:21:52 UTC
By "packaging files", I mean using the files being copied into the image in the Dockerfile in lines 61 and 64. If so, I believe the files should be linked here for the Review (let me know if you'd like me to go through that repository instead).

As for the image name, I believe the $FGC has been dropped from the guidelines, where we should now use just the main component name in the package. Moreover, shouldn't this bug name be the same as the image name and component, i.e., php? Then you could manipulate the image tag depending on the base image used to point to the proper php version you want to ship. Otherwise, we'd have to package/review this image multiple times for different Fedora releases. Thoughts?

I am also pinging Clement here to hear his ideas on this one :)

Comment 6 Clement Verna 2020-08-03 10:22:04 UTC
I believe the php s2i image is already available https://src.fedoraproject.org/container/php, it has just not been built in a while :(

Comment 7 Athos Ribeiro 2020-08-03 12:03:35 UTC
Any objections on closing this as a duplicate of BZ#1445784?

Comment 8 cragr 2020-08-04 17:18:24 UTC
(In reply to Clement Verna from comment #6)
> I believe the php s2i image is already available
> https://src.fedoraproject.org/container/php, it has just not been built in a
> while :(

Correct.  I would like to update these images if possible.  The Fedora 31 version would include PHP7.3 an Fedora 32 would include PHP7.4.

Comment 9 Athos Ribeiro 2020-08-07 22:08:05 UTC
In this case, you should contact rpitonak ( the owner of https://src.fedoraproject.org/container/php). For the PRs in that repo, he seems to be inactive. If that is the case, you could start a non-responsive packager process.

Packaging this under a different name does not seems to be the way forward here though.

Comment 10 cragr 2020-08-18 17:12:07 UTC
Closing with recommendation of contacting rpitonak.