search

WASdev / ci.docker.websphere-traditional

Dockerfiles for WebSphere Application Server traditional
Apache License 2.0
171 stars 192 forks source link

WebSphere 8 docker images removed from docker hub #141

Closed ryandens closed 5 years ago

ryandens commented 5 years ago

I'm curious why the WebSphere 8 docker images were removed from docker hub. These images were extremely useful for me and my team for manually testing the compatibility of our software with WebSphere on our own machines. Is there significant work maintaining them? Is there a way to archive them instead of deleting them?

arthurdm commented 5 years ago

hey @ryandens - thanks for the feedback. Our strategy for Docker containers is to support WebSphere Liberty (continous releases) and traditional WebSphere v9 only. The older v8 images were out of date and were not being updated - so they had older Ubuntu images with vulnerabilities, etc.

V9 contains the latest security fixes and improvements for traditional WAS. Are you able to try out v9 as a migration target? We have a Migration Toolkit that should help you out.

ryandens commented 5 years ago

We're not using WebSphere 8 in production at all, but our customers are. We were using these docker images simply to test the compatibility of our software with WebSphere 8. Given that the license for these docker images on docker hub states:

Note that this license does not permit further distribution and restricts usage to a developer machine.

I don't see why keeping these images up introduces people who use these images to any risks. We already use the docker images for WebSphere v9 in testing as well, we just don't want to lose test coverage.

moilejter commented 5 years ago

+1 - we are still running WS8 in production, and an upgrade to WS9 is not in the cards for us, in the short term... So having the WS8 images available for us to quickly build test envs with would be a win.

arthurdm commented 5 years ago

thanks for the feedback guys. Are you referring to V8.0 or V8.5?

I believe that with the latest PR #143 from @DSTOLF you will be able to download your specific WAS versions and use the same Dockerfile.offline artifact to build your images.

DSTOLF commented 5 years ago

I haven't tested the offline buid with Websphere V8.5, but I suppose it should work.

I have free time to test it this week and I'd be happy to help, but I'm unable to find a valid repository URL and product ID to download V8.5 through installation manager.

I have tried both

/opt/IBM/InstallationManager/eclipse/tools/imutilsc saveCredential -userName <MyID> -userPassword <MyPswd>-secureStorageFile /tmp/secureStore  -masterPasswordFile /tmp/secureStorePwd -url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.DEVELOPERSILAN.v85

and

/opt/IBM/InstallationManager/eclipse/tools/imutilsc saveCredential -userName <MyID> -userPassword <MyPswd>-secureStorageFile /tmp/secureStore  -masterPasswordFile /tmp/secureStorePwd -url  http://www.ibm.com/software/repositorymanager/com.ibm.websphere.DEVELOPERS.v85

And both returns "No Package were found" when I run /opt/IBM/InstallationManager/eclipse/tools//imcl listAvailablePackages

If it's still possible to download tWAS 8.5 thorugh IM and someone could provide me with the repository URL and product ID, I can run some tests.

ryandens commented 5 years ago

Hi @arthurdm, thanks for the info. Our developers have the image cached locally, but I'll make sure to document this in case we need it.

I guess I just object to the principle of deleting things off of docker hub, seems silly to have us all repeat this work to use the Dockerfile.offline when docker hub exists to share images. Just because the image will not be maintained or updated does not mean it doesn't provide value.

ryandens commented 5 years ago

oops, didn't mean to close the issue 😨. Feel free to do so though if you guys feel this is resolved

moilejter commented 5 years ago

thanks for the feedback guys. Are you referring to V8.0 or V8.5?

Sorry - in our case, we're using v8.5.5.6 (fixpack 14?). I think one of the people in our team still has an image downloaded a couple of months back in her local docker instance - so we may be able to just share that image locally. But I would still like to be able to build such an image from scratch, as long as we're still running v8.5... I will ask our middleware team whether we have the repository and/or product ids, to see if we can help test that offline build, on our end.

arthurdm commented 5 years ago

thanks @DSTOLF! I am not sure what the URL would be, maybe @patricktiu knows? But, you could retrieve the binaries manually from Fix Central, unzip them, and them point IM to that local repo. I found an old branch that demonstrated this pattern.

DSTOLF commented 5 years ago

@arthurdm I've found the problem... the install script from v9 installs two packages: $PRODUCTIDand com.ibm.java.jdk.v8.

There's no JDK available in WAS8.5 repository.

To make it compatible with both, WAS9 and 8.5, I'm refactoring the Installation Manager script. I'm running some tests and will add the commit soon.

Regards, Daniel Stolf

DSTOLF commented 5 years ago

Ok...

I think the application server is working, but some parameters passed to /opt/IBM/WebSphere/AppServer/bin/logViewer.sh on the start_server script are not compatible with previous versions of WAS.

I think further debugging is needed. I think it would be better to create a different folder vor WAS8.5, as the startup scripts would be different.

I'm changing PR #143 to WIP, because I'll need some guidance on this.

arthurdm commented 5 years ago

awesome work @DSTOLF! thanks a lot for taking the time to do this.

Yes, the new logViewer item is only applicable for 9.0.0.10+. I think it's very reasonable to separate the WAS8.5 Dockerfile.

DSTOLF commented 5 years ago

@arthurdm I have added the 8.5.x folder, run some tests and it seems to be working fine.

I used 9.0.0.9 as a base, so config-props and app deployment procedures were NOT carried over from the newer versions, as I'm currently unable to commit any time to run tests, but somebody else can do that after (or if) my changes are pushed to master. Since those won't be published images, I don't think it shuld be an issue.

I think some disclaimer for the old unsupported versions should be added later, but that's your call ;)

Regards.

naumanna commented 5 years ago

I used the 8.5.x build files created under #143 to build an 8.5.5.14 image and upload it to Docker Hub. The image name is ibmcom/websphere-traditional:8.5.5.14-profile. As @arthurdm has noted in the comments here, it won't be a supported image, but it is available for people to pull.

arthurdm commented 5 years ago

Thanks @naumanna!

@ryandens / @moilejter - fyi ^

perazzi commented 4 years ago

It seems that the images for 8.5.5 were removed again? @ryandens @DSTOLF

gmarcy commented 4 years ago

my guess is that the process to clean up when we added 9.0.5.2 would have removed anything older than 9.0.5.0 since we only keep the last 3 releases.

ghost commented 4 years ago

You are not alone perazzi, we are on 8.5 at work.

ChowDavid commented 4 years ago

Please note IBM. Company are think not to use IBM product. there are many container in the market. The docker for IBM WAS 8.5.5 is a good start to adapt the existing product during development state can testable. What if we dont have the IBM container for testing. then we may use other container. and may be finally remove all those code related to IBM product. We can just use spring boot for enterprise application. Please help to resume and release those exisitng container in docker. and keep the market space. Choice to use IBM or not is by us the developer and client. Choice to refuse to support the product in the market was by IBM. WAS migrate from WAS 8.5.5 to 9 is the other story and company may not has any budget. Please keep those image in docker in order to keep the market.

jblayneyXpanxion commented 4 years ago

@naumanna would you be able to push this image again? It would be very much appreciated.

@ryandens / @moilejter - fyi ^

gmarcy commented 4 years ago

I am in the process of resurrecting the 8.5.5.x side of the build process, we should have images again starting with 8.5.5.16, just working on getting the resources together to have the builds happening regularly

naumanna commented 4 years ago

I'm not with IBM any more to be able to build the 8.5.5 images again. @gmarcy, I had originally just manually built the images for the latest 8.5.5.x fix pack (8.5.5.14 at the time) using the 8.5.x build files and uploaded them to Docker Hub. We weren't updating them regularly or updating for new fix packs, that was only done for 9.0.0.x.

wheredevel commented 4 years ago

I used to have ibmcom/websphere-traditional:8.5.5.14-profile perfectly working. Used for testing compatibility issues. But my locally cached image was removed sometime ago due to space shortage.

Is there any way to get the 8.5.5.14 image again? Or any 8.5.x ? Please, help!

gmarcy commented 4 years ago

We are still working on the build resources to automatically produce and maintain images, but the Dockerfile information is already delivered to this repository, so you should be able to build an 8.5.5.17 image yourself following the instructions in that folder.

https://github.com/WASdev/ci.docker.websphere-traditional/tree/master/docker-build/8.5.5.17

wheredevel commented 4 years ago

We are still working on the build resources to automatically produce and maintain images, but the Dockerfile information is already delivered to this repository, so you should be able to build an 8.5.5.17 image yourself following the instructions in that folder.

https://github.com/WASdev/ci.docker.websphere-traditional/tree/master/docker-build/8.5.5.17

Thanks, I will try that now.