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.
15 Replies
- JasonEpstein
Employee
Another thing I realized today when working with another customer with a similar permissions issue: if you want to work with your existing clone of the repo, you will also need to enable executable permissions for user, "other", on all directories. This is also required for access to these files.
From the application-study-tool/ directory, run "chmod -R o+X services" (you might need "sudo" before this command as well). Note the capital "X", which will only change the permissions of the directories -- not the files.
MikesisavI missed this entry as I had to hit a hyperlink. Not sure why it just did not thread it lower. Whatever. I will try this today instead of "chmod -R o+r ." from yesterday as I just saw it and report back. Thanks, again, Jason.
- Mikesisav
Jason,
Happy New Year.
I was able to run "chmod -R o+r ." and then successfully, which seems to move then next command forward from last year's work "
sudo docker run --rm -it -w /app -v ${PWD}:/app --entrypoint /app/src/bin/init_entrypoint.sh python:3.12.6-slim-bookworm --generate-config". The last lines for that last command are "
2026-01-07 22:37:39,991 - INFO - Successfully wrote data to './services/otel_collector/pipelines.yaml'.
2026-01-07 22:37:39,997 - INFO - Successfully wrote data to './services/otel_collector/receivers.yaml'."
I then tried to run "docker compose up" next and get this "
unable to get image 'grafana/grafana@sha256:6128afd8174f01e39a78341cb457588f723bbb9c3b25c4d43c4b775881767069': permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.51/images/grafana/grafana@sha256:6128afd8174f01e39a78341cb457588f723bbb9c3b25c4d43c4b775881767069/json": dial unix /var/run/docker.sock: connect: permission denied"
This still reads like a permission issue, potentially?
Thank you for your time and efforts.
- JasonEpstein
You're close. It looks like you just need "sudo" before "docker compose up", and you should get past the permissions issue.
So:sudo docker compose upAlso, there shouldn't be a quote (") after the previous docker command, but it looks like you have it working.
- Mikesisav
Can't seem to see the threaded Forrest through the threaded trees here. Only one cup of coffee. Will update after doing some more testing. Thank you.
