Forum Discussion
AltostratusAST Configuration Assistance
All, I had AST configured on a RHEL platform and the 3000 port as web available.
Something changed in our environment and I had to wipe away the docker configuration and I am starting from scratch on the same RHEL instance.
Docker is working as "sudo docker run hello-world" states "This message shows that your installation appears to be working correctly."
I deleted the old application-study-tool and added the folder from the tarball to my home directory.
I copied and edited the below :
cp .env-example .env
cp .env.device-secrets-example .env.device-secrets
vi ./config/ast_defaults.yaml
vi ./config/bigip_receivers.yaml
That all took like before the first installation.
When I run this " docker run --rm -it -w /app -v ${PWD}:/app --entrypoint /app/src/bin/init_entrypoint.sh python:3.12.6-slim-bookworm --generate-config "...I get the error :
"docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/app/src/bin/init_entrypoint.sh": stat /app/src/bin/init_entrypoint.sh: no such file or directory: unknown"
That is where I am stuck.
Python version is python3.11
Wanted to reach out here first before I potentially tried it on another RHEL box - clean install.
Any help or direction would be appreciated.
3 Replies
- JasonEpstein
Employee
Hi Mikesisav
Can you check your current working directory? It should be in /[your]/[ast]/[path]/application-study-tool
You can run "pwd" for this.Can you also check your default permissions by running "umask"? If it ends with a 7, new files, by default, will be created with RWX permissions disabled for "other" users (which these containers run under).
(If you are curious about what this command does, see the post, "What is "umask" and how does it work?")If you post the output of "pwd" and "umask" here, we'll also take a look.
MikesisavThanks, Jeffrey.
Got something different this time. If you can think of any other commands to try, I would appreciate it.
sudo docker run --rm -it -w /app -v ${PWD}:/app:z --entrypoint /app/src/bin/init_entrypoint.sh python:3.12.6-slim-bookworm --generate-config
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/app/src/bin/init_entrypoint.sh": stat /app/src/bin/init_entrypoint.sh: no such file or directory: unknown- Jeffrey_Granier
Hi Mikesisav ,
You could try adding the "z" flag: sudo docker run --rm -it -w /app -v ${PWD}:/app:z --entrypoint /app/src/bin/init_entrypoint.sh python:3.12.6-slim-bookworm --generate-config
lowercase "z" relabels the volume as shared which lets container to read/execute the script.
uppercase "Z" handles for private relabeling for stricter isolation.
Then go ahead and try to start the services
