I’m sure anyone who cares knows that APEX 19.2 was officially released on Friday. I did an upgrade of one of our development instances straight away and it worked fine. it’s subsequently gone to a bunch of other development instances. I’ll be pushing to get this out to production as quickly as possible.
Over the weekend I worked through a bunch of my GitHub stuff.
Vagrant : I’ve updated all my Vagrant builds to use APEX 19.2 and the latest versions of Tomcat 9 and OpenJDK 11. I was using newer versions of OpenJDK, but it seemed a bit silly, so I reverted back to the long term support release. I tried updating the base box to ‘bento/oracle-7.7’, but it kept giving me timeouts, so I’ve reverted back to ‘bento/oracle-7.6’ for the moment.
Docker : Same as above, I’ve updated all my Docker builds to use APEX 19.2 and the latest versions of Tomcat 9 and OpenJDK 11. I noticed oraclelinux:8-slim was behaving a little strangely. I thought it was a PATH issue, but I need to spend some time to understand what is happening. It seems you can’t run basic commands like dnf during the build phase. It’s probably something stupid I’m doing, but for now I’ve switched from oraclelinux:8-slim to oraclelinux:8. Just making that switch made everything work as expected.
My Docker builds within the company have gone through a similar process, so as I’m rolling out APEX 19.2 to the databases, I’m also switching the ORDS containers over to the new images. You gotta love containers!
I guess I’ll be working through all this again when the next version of ORDS and SQLcl drop. 🙂
2 thoughts on “APEX 19.2 : Vagrant and Docker Builds”
Hi Tim. Nice post as usual. One question for you. Why don’t you use yum to install packages since dnf has some issues on docker. As I recall, for debian/ubuntu docker images, docker build tool generate a warning for using APT install tool and instruct me to use APT-GET tool instead.
Danut: Yum doesn’t work either. 🙂
Comments are closed.