You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
latest-devel image: sudo is broken (missing /usr/bin/sudo) #7
The ghcr.io/bounverif/esmini:latest-devel image ships a sudo wrapper from gcc-toolset-14 at /opt/rh/gcc-toolset-14/root/usr/bin/sudo, but the actual sudo package is not installed. Since gcc-toolset-14 is on $PATH, calling sudo finds the wrapper, which fails:
$ sudo whoami
/opt/rh/gcc-toolset-14/root/usr/bin/sudo: line 41: /usr/bin/sudo: No such file or directory
This breaks VS Code devcontainer usage — the devcontainer tooling relies on working sudo for any non-root remoteUser.
Reproduction
docker run --rm ghcr.io/bounverif/esmini:latest-devel sudo whoami
# /opt/rh/gcc-toolset-14/root/usr/bin/sudo: line 41: /usr/bin/sudo: No such file or directory
Suggested fix
Install the sudo package in the esmini-devel Dockerfile:
RUN dnf install -y sudo && dnf clean all
Workaround
Downstream Dockerfile can install it themselves:
FROM ghcr.io/bounverif/esmini:latest-devel
RUN dnf install -y -q sudo && dnf clean all
Hi @doganulus I am currently integrating ASAM-OSI-Utilities into esmini with this PR. In the process I saw that the dev container from this repository is used in esmini and that the mentioned additional configurations are missing. I was fixing it locally and thought I drop by to report it. The integration of ASAM OSI entailed a lot of updates to the build instructions and therefore I tested on all platforms.
The goal I am following is to update OSI to the newest v3.8.0-rc1 and use the new language specific bindings which are separate repositories and integrate these via a tooling repo which impements the reading and writing of OSI trace files including the new MCAP multi channel spec.
This allows for the native usage of esmini output in combination with the Lichtblick framework which is the continuation of Foxglove Studio maintained by BMW. It allows for building custom plugins where a visualization plugin for ASAM OSI Data is available opensource as well here.
Activity
doganulus commentedon Apr 2, 2026
@jdsika This repo is out-of-date. It was mostly an external experiment.
What sparked your interest in this repository? I may have some time over the coming weeks to update it.
jdsika commentedon Apr 2, 2026
Hi @doganulus I am currently integrating ASAM-OSI-Utilities into esmini with this PR. In the process I saw that the dev container from this repository is used in esmini and that the mentioned additional configurations are missing. I was fixing it locally and thought I drop by to report it. The integration of ASAM OSI entailed a lot of updates to the build instructions and therefore I tested on all platforms.
The goal I am following is to update OSI to the newest v3.8.0-rc1 and use the new language specific bindings which are separate repositories and integrate these via a tooling repo which impements the reading and writing of OSI trace files including the new MCAP multi channel spec.
This allows for the native usage of esmini output in combination with the Lichtblick framework which is the continuation of Foxglove Studio maintained by BMW. It allows for building custom plugins where a visualization plugin for ASAM OSI Data is available opensource as well here.
jdsika commentedon Apr 2, 2026
For reference, we've worked around this in the esmini devcontainer with commit
0fc6f59fon thefeat/osi-utilities-integrationbranch:sudoviadnf installubuntuuser with passwordless sudo via/etc/sudoers.dsudois installed before writing the sudoers fileVerified end-to-end: devcontainer starts, full OSI two-phase build succeeds, and all 53 unit tests pass.