Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    10
  • Views views
    804
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Docker Client in Kubernetes (aos.c:488 error)

Kirk Vogen

Has anyone gotten the accurev client working in a Kubernetes pod? We have made a Docker container with the AccuRev client. When running in our Amazon EKS cluster, we get this error following a login:

e.g.

accurev login <myuser> # Successful!
accurev info #F ails...Client time:    2022/05/03 14:12:10 UTC (1651587130)
Server time:    2022/05/03 14:12:10 UTC (1651587130)
-Error- 1 - aos.c:488 - Failure getting system drive table

The above command work just fine in a plain old Docker. They also work just fine in a local Kubernetes cluster via minikube. It only fails in our cluster in Amazon EKS.

It seems that that cluster doesn't allow something filesystem-wise that the accurev client needs. If only I could see the source code of aos.c, line 488 to figure out what it is doing!

Any thoughts?

Tags:

  • Verified Answer

    +1

    Problem solved. The accurev CLI looks at /etc/mtab  to examine filesystem mounts. In certain Kubernetes clusters, that file didn't exist. The solution was to ensure that a symlink from /proc/mounts to /etc/mtab exists.

  • 0 in reply to Kirk Vogen

    This will work for insecure "rootfull" dockerd, but it is still an issue for "rootless" podman. Is there any way to have the accurev CLI not rely on /etc/mtab?

    Answer, I was able to workaround by adding "-v /etc/mtab:/etc/mtab" to the podman run command.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.