Skip to content

Docker Environments Breaking #1076

@javawolfpack

Description

@javawolfpack

Describe the bug
I build a new grading container and when the container runs, the PATH environments no longer match what was built. As an example for Rust have the following:

# System-wide locations so all users share one toolchain/cache
ENV RUSTUP_HOME=/usr/local/rustup \
    CARGO_HOME=/usr/local/cargo \
    PATH=/usr/local/cargo/bin:$PATH

And the PATH in the container when grading or debug shell you can SSH into doesn't have cargo's bin in the path. I also tried setting the PATH in /etc/environment or profile and that resulted in the container fully failing to launch/work at all.

INGInious installation details

  • Version: 0.9.1

To Reproduce
Steps to reproduce the behavior:

  1. Create grading container w/ modified PATH
  2. Submit

Expected behavior
PATH should be the same as when running the container on it's own outside of the INGInious system or kind of defeats the point.

Additional context
This has now also been detected at least in the debug mode of another container, least working for grading but somehow lacks g++ when you launch the debug shell. Seems like the same issue that somehow the way you're launch the docker containers is corrupting the system PATHs

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions