Skip to main content
coldbhop
Participant
June 8, 2026
Question

Permission issues running coldfusion2025 in OpenShift

  • June 8, 2026
  • 1 reply
  • 54 views

First of all, I have no coldfusion experience at all. So when answering or asking for coldfusion specifics, please try to keep your answer/question somewhat lightweight :)

I’m trying to setup a minimal cfusion2025 image that runs on openshift. I currently have some issues with the image’s existing cfuser or the pod’s permissions.

Dockerfile:

FROM adobecoldfusion/coldfusion2025:latest

USER root

COPY ./sources /app

EXPOSE 8080 8500


Pod logs:

Skipping Configuration and Setting Wizard
sed: couldn't open temporary file /opt/coldfusion/cfusion/lib/sedFCBEbg: Permission denied
sed: couldn't open temporary file /opt/coldfusion/cfusion/lib/sedMKjs1Y: Permission denied
Updating webroot to /app
Configuring virtual directories
chown: changing ownership of '/app': Operation not permitted (os error 1)
chown: changing ownership of '/app/index.cfm': Operation not permitted
chown: changing ownership of '/app/test': Operation not permitted
chown: changing ownership of '/app/test/cfm': Operation not permitted
chown: changing ownership of '/app/test/cfm/index.cfm': Operation not permitted
chown: changing ownership of '/app/crossdomain.xml': Operation not permitted
chown: changing ownership of '/opt/startup/coldfusion': Operation not permitted (os error 1)
chown: changing ownership of '/opt/startup/coldfusion/importCAR.cfm': Operation not permitted
Setting up cfsetup alias
Password: su: Authentication failure
Updating password
/opt/startup/start-coldfusion.sh: line 453: /opt/coldfusion/cfusion/lib/password.properties.tmp: Permission denied
mv: cannot stat '/opt/coldfusion/cfusion/lib/password.properties.tmp': No such file or directory
/opt/startup/start-coldfusion.sh: line 455: /opt/coldfusion/cfusion/lib/password.properties.tmp: Permission denied
mv: cannot stat '/opt/coldfusion/cfusion/lib/password.properties.tmp': No such file or directory
chown: changing ownership of '/opt/coldfusion/cfusion/lib/password.properties': Operation not permitted (os error 1)
Language not changed
Missing license file, invalid license file path, or incorrect configuration file detected.
Edition not provided
Deployment Type not set , set to default(Production)
No Modules to be installed!
No Modules to be imported!
Secure Profile: Disabled
Profile not set , set to default(Development Profile)
allowed admin IP List not set
No settings to be imported!
External Addons: Disabled
External Session Storage: Disabled
chmod: Operation not permitted (os error 1)
chown: changing ownership of '/opt/coldfusion/cfusion/lib/licenseinfo.properties': Operation not permitted (os error 1)
chgrp: changing group of '/opt/coldfusion/cfusion/lib/licenseinfo.properties': Operation not permitted (os error 1)
Starting ColdFusion
Starting ColdFusion 2025 server ...
Password: su: Authentication failure
There has been an error starting ColdFusion 2025 server, please check the logs.
Password: su: Authentication failure
[] Checking server startup status...


I have a Dockerfile version where I managed adjusting all the permission issues and deleting/recreating the cfuser in my Dockerfile with a specific compatible uuid for openshift (and running the Deployment/Container with that specific user) which just leaves me with these repeated logs:

Starting ColdFusion 2025 server ...
Password: su: Authentication failure
There has been an error starting ColdFusion 2025 server, please check the logs.
Password: su: Authentication failure
[] Checking server startup status...
Password: su: Authentication failure
[] Checking server startup status...
Password: su: Authentication failure


But I’d like to think that my Dockerfile shouldn’t require so many custom adjustments and should just work out of the box.

I found that there are several lines in the startup-coldfusion.sh that attempt to chown/chgrp which cause the “Operation not permitted” logs:

chown -R cfuser /app
chown -R cfuser /opt/startup/coldfusion


Have I perhaps missed some required configuration during my setup?

    1 reply

    Charlie Arehart
    Community Expert
    Community Expert
    June 8, 2026

    While I have zero experience with openshift, I can say that you should NOT need to use that USER command, at all, for the image to be able to run a container in docker, kubernetes, podman, etc.

     

    It seems all the more odd that you’re setting it to root. I thought you were finding that openshift had issues running with the built-in cfuser (that the container runs CF as, and for which the container startup scripts set permissions within the container).

     

    If no one here has more for you, I’d propose you send this to cfsup@adobe.com.

     

    There was indeed a plan originally for them to support openshift, when the CF images first came out during the CF2018 timeframe. I’d not heard more about it since then. Perhaps they found it had requirements whose effort to support exceeded the interest among paying CF customers.  You may find they can readily clarify why it possibly can’t be (or per perhaps can be) made to work.

    /Charlie (troubleshooter, carehart. org)