8000 latest-devel image: sudo is broken (missing /usr/bin/sudo) · Issue #7 · vevalabs/exmini · GitHub
[go: up one dir, main page]

Skip to content

latest-devel image: sudo is broken (missing /usr/bin/sudo) #7

Open

Description

@jdsika

Problem

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

This is what we currently do in the esmini devcontainer.

Activity

  1. doganulus commented on Apr 2, 2026

    @doganulus
    Member

    @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.

  2. jdsika commented on Apr 2, 2026

    @jdsika
    Author

    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.

  3. jdsika commented on Apr 2, 2026

    @jdsika
    Author

    For reference, we've worked around this in the esmini devcontainer with commit 0fc6f59f on the feat/osi-utilities-integration branch:

    • Install sudo via dnf install
    • Create the ubuntu user with passwordless sudo via /etc/sudoers.d
    • Reorder the Dockerfile so sudo is installed before writing the sudoers file

    Verified end-to-end: devcontainer starts, full OSI two-phase build succeeds, and all 53 unit tests pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0