Errors in docker run
Has anyone seen this before? I'm new/bad at Docker and not even sure how to debug.
$ sudo docker logs <container>
[INFO] Starting InterSystems IRIS instance IRIS...
[INFO] Unable to read the startup.last file to identify the location of the write
image journal file (IRIS.WIJ) that was last in use by this instance. Please
fix the permissions of the startup.last file.
** Startup aborted **
Starting IRIS
Recovery failure. Startup aborted.
[ERROR] Command "iris start IRIS quietly" exited with status 256
[ERROR] See the above messages or /usr/irissys/mgr/messages.log for more information
[FATAL] Error starting InterSystems IRIS
Comments
Permission points to some missing user privileges
start your container in foreground (no -d switch) to see the full log with details
The full log I get (running without -d) is exactly the same as above.
is the rebuild of the container an option?
Telling you something you already know: You've got some bad state in your container image or in the persistent storage.
I think we'd need to see more to be able to help:
* What's the command you're using to run the container? All the environment variables and mount points is super-important here
* What's the container you're running? If its your own, maybe the Dockerfile would help
I'm running a container based on intersystemsdc/iris-community:latest. Was able to get into the filesystem and found weird ??????s in permissions, similar to https://stackoverflow.com/questions/52195175/strange-file-permission-in… - I'm going to try rebuilding and if that doesn't work try restarting the docker service on the host where things aren't working.
https://stackoverflow.com/questions/72917224/ls-l-in-docker-shows-quest… has better info and I was able to work around the issue in question by doing something I don't want to admit to doing. (Ultimately the root cause is old infrastructure where I'm deploying the container.)
Hi Timothy, without admitting to something, what did you do? I've a similar issue.