[{"_1":2,"_179":-5,"_180":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_155":156},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_144":-5,"_145":11,"_146":21,"_147":11,"_148":-5,"_149":11,"_150":-5,"_151":152,"_153":91,"_154":-7},"canonicalUrl","https://hub.docker.com/r/ihalaij1/grading-base/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","ihalaij1","reponame","grading-base","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2023-06-21T11:31:31.583196Z","description","","is_private","last_updated","2023-06-21T11:50:54.973234Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.oci.image.index.v1+json","name","pull_count",975,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","A docker container that includes a stable Debian Linux and convenience commands for grading a student submission.\nCommands include tools from capturing the test output to submitting a feedback back to the grading service.\n\nThis container is just a base and does not include tools for different programming and scripting languages.\nThus, actual grading/assessment containers should derive from this container via the FROM instruction in their Dockerfiles.\n\nYou can find many grading containers on [the apluslms page on docker hub](https://hub.docker.com/u/apluslms/).\nContainers starting with `grade-` are relevant for this purpose.\n\nVersion of grading base has format `.`.\nMajor is updated when there is backwards incompatible change.\nFor example, when deprecated tool is removed.\nMinor number is updated every time there is something new, where that bug fixes, added features or update on the debian base image.\nDerived containers typically use format `-u`,\nwhere tool version is the version from upstream, grading-base is the version of this container and update is number that indicates update on containerisation.\nSo, for example, grade-python `3.5-2.2u1` means that there is python 3.5 on top of grading-base 2.2 and it's first update after initial release.\nUpdate part is optional and can be omitted.\n\n# The container entry point, the grade wrapper\n\nContainer has grade wrapper `/gw` set as the entry point.\nThis means that everything executed within this container (or derivative) is executed through this script.\n\nThe wrapper will take care of redirecting output (stdout and stderr) to `/feedback/grading-script-errors`.\nIn addition, the script will make sure that the working directory is set correctly.\nAfter the grading script has been executed, the wrapper will execute `grade`.\nThus, the grading script does not need to call `cd` or `grade` anymore.\n\nThe wrapper has three different operations, based on the first argument.\n\n1. If the first argument starts with `/bin/` or is `--exec`,\n then arguments are executed and the wrapper itself stops here.\n No redirections are done and `grade` is not executed.\n\n2. If the first argument is `--sh`, then rest of the arguments are evaluated with `sh -c \"$*\"`.\n This makes strings with quoted text possible in mooc-grader environment.\n\n3. The typical case. Argument list is executed as is.\n\nThe exit code from the grading script is stored in the grading-script-errors, but the grade wrapper always exits with 0.\n\n# Filesystem layout\n\n* `/submission/user`\n\n Files for the solution submitted by the student are stored here.\n This path can be used as working directory.\n\n* `/exercise`\n\n Exercise files are mounted here in a read only mode.\n With mooc-grader, that means the path you entered in `mount`.\n Typically, this includes `run.sh` and unit test files.\n\n* `/feedback`\n\n Grading script should store feedback in this path.\n Most utility commands do so, including `capture`, `testcase` and `grade`.\n In the future, mooc-grader will read files from this path instead of expecting a post request.\n\n * `/feedback/points`:\n\n Final points.\n Valid format for the data is `/` e.g. `5/10`.\n You can use `points` to update this file.\n Points are read by `grade`.\n\n * `/feedback/out`:\n\n Feedback that is going be presented in the LMS.\n Typically, data is in html format.\n You should use `pre` to wrap plain text to html.\n You can capture feedback with `capture pre `, for example.\n\n * `/feedback/err`:\n\n Error messages from a student or a testing code.\n If present, `grade` will append this inside a pre tag at the end of the out file.\n This file typically contains stderr from the test code.\n For example, `capture` redirects stderr to this file.\n If stderr is normal output (e.g. with python unit tests), then you should consider using `err-to-out`.\n\n * `/feedback/grading-script-errors`:\n\n Errors that should be visible only to the staff.\n This file is added as a part of `grading_data` with key `errors` and send to the grading service.\n Then, data can be shown in the LMS to the course staff.\n Data is expected to be plain text messages from `run.sh` and other tools.\n By default, `/gw` redirects stdout and stderr from the `run.sh` to this file.\n\n * `/feedback/submission-set-error`:\n\n If this file contains `true`, then the submission is set in an error state in the LMS.\n You can use `set-error` in your script to set this file.\n\n* `/feedback/`\n\n A single feedback item.\n A set of these directories is considered the feedback list.\n Typically, one folder matches one test case.\n For now, this feedback list is not fully supported and the tool `create-test-feedback` is provided to render these directories to `/feedback/out`.\n Nevertheless, this allows building tools and scripts that export feedback in this format.\n In future, different templates can be used to render the feedback list in the grading service.\n The `grade` tool will automatically merge these directories to a single html file, if grading service doesn't support feedback as a list.\n\n For every numbered path (feedback item), there can exists any number of files, but following files are typical.\n Following files are supported by `create-test-feedback` and a basic template on the grading service.\n More advanced or specific templates can of course deviate from those.\n\n * `.../title`: A title or a display name for this feedback item.\n * `.../status`: The status of this feedback. Valid values: `skipped`, `passed`, `failed`, `error`.\n * `.../points`: Points given from this item.\n * `.../max_points`: Maximum points that could be given from this item.\n * `.../out.txt`: Stdout from the test.\n * `.../err.txt`: Stderr from the test.\n\n\n# Utility commands\n\nFollowing utility commands are provided in the path.\n\n* `testcase [-t title] [-p points_on_success] [-s only_if_zero] CMD...`\n\n Defines a single test case.\n Useful when running multiple commands for grading.\n Creates `/feedback/` directory with increasing number for every call.\n\n If `title` is provided, it's stored in `/feedback//title`.\n\n If `points_on_success` is provided, it will be written to `/feedback//max_points`.\n If CMD exits with 0, then it will also be written to `/feedback//points`.\n\n If `only_if_zero` is provided and not 0, then CMD is not executed and `testcase` exits with non-zero exit code.\n\n Status of this test is stored in `/feedback//status` accordingly.\n\n* `capture [-o out] [-e err] [-u user] CMD...`\n\n Changes the ownership of the working directory to `user`,\n executes the command as `user`,\n and captures the stdout to `out` and the stderr to `err`.\n In addition, `capture` ensures that the environment does not contain `REC` or `SID` (the variables used for posting feedback).\n\n By default `user` is `nobody`, `out` is `/feedback/out` and `err` is `/feedback/err`.\n\n For example, `capture pre ./my_test` will execute `./my_test` as `nobody` and redirect stdout and stderr to `/feedback/out` and `/feedback/err`.\n\n If you need to run captured code as root, then use `capture -u root`.\n\n* `asuser [-u user] CMD...`\n\n Drops privileges to the `user` and executes `CMD`.\n See command `capture`, which does output redirection before calling `asuser`.\n\n NB `asuser` must be executed as the user `root`, as we can only drop privileges.\n\n In addition to privileges, `asuser` makes following changes to the environment variables:\n\n * set `USER` to the `user`\n * set `HOME` to the home path of the `user`\n * set `UID` to the numerical id of the `user`\n * set `GID` to the numerical id of the main group of the `user`\n * drop locations ending in `*/sbin` from the `PATH`\n * remove `REC` and `SID` (used to post feedback to MOOC-Grader)\n\n _New in version 2.8._\n\n _Changed in version 3.1_: Added environment variables `UID` and `GID`\n\n* `pre [-c class] CMD...`\n\n Wraps the stdout of the command into `

` HTML element and escapes any HTML inside.\n    Can be chained, e.g. `capture pre ./my_assessment_code.sh arg1 arg2`\n\n    Option `-c` can be used to set HTML class for the element.\n\n* `points  [only_if_zero]`\n\n    Add `points` to given and maximum points in `/feedback/points`.\n    If the file exists, it will be updated.\n    If `only_if_zero` is given and not zero, then only maximum points are changed.\n\n    This can be used in conjunction with `capture` to give points conditionally.\n    For example,\n\n    ```\n    capture ./my_assessment_code.sh\n    points 10 $?\n    ```\n\n    where `$?` is the exit code from `capture`.\n\n* `title [-c class] [-e element] [-O] `\n\n    Writes `text` inside HTML element `element` to `/feedback/out`.\n    The element is `h1` by default, but can be changed with `-e`.\n\n    Option `-c` can be used to set HTML class for the element.\n\n    Flag `-O` changes the output to stdout.\n\n* `grade [points/max]`\n\n    Submits the feedback back to the grading service.\n    The grade wrapper will execute this command after the grading script.\n    This command exits without changes if it is executed for the second time,\n    thus grading script can call this too, but is not required to.\n\n    If no argument is provided, there isn't `/feedback/points` and any of `/feedback/` directories exists,\n    then `create-test-feedback` is executed before reading the feedback.\n\n    Gets granted points in priority order from:\n    a) argument in format \"5/10\"\n    b) /feedback/points file in format \"5/10\"\n    c) /feedback/out including lines \"TotalPoints: 5\" and \"MaxPoints: 10\"\n\n    Gets feedback as HTML from /feedback/out,\n    and wraps /feedback/err into pre with `alert-danger` class at the end.\n    If /feedback/appendix exists it will be included at the very end.\n\n* `replace [-o out_file] REPLACE=in.txt [ANOTHER=another.txt] `\n\n    A simple string replace tool for handling untrusted inputs.\n    The tool reads `template_file` and replaces all shell variables given as arguments with contents of the given files.\n    For example, when given `REPLACE=in.txt` and `template_file`, then all instances of `$REPLACE` and `${REPLACE}` in `template_file` are replaced with contents of the file `in.txt`.\n    Note that, if there exists a new line in the end of `in.txt`, it will be removed when the file is read.\n\n    Please notice, the only valid shell variable names can be used, i.e. names consisting of letters, numbers and the underscore.\n\n    This tool is wrapper around `envsubst` and the above command is basically the same as the following:\n\n    ```sh\n    REPLACE=$(cat in.txt) ANOTHER=$(cat another.txt) \\\n        envsubst '$REPLACE $ANOTHER' < in_file > out_file\n    ```\n\n    Keep in mind that for some purposes `sed` and `envsubst` are simpler,\n    but when handling user input, `replace` might be cleaner.\n\n* `stdio-diff [-c] [-s] [-S] [-p pass_text] [-P] [-f fail_text]   CMD...`\n\n    Simple text comparison wrapper based on `diff`.\n    Given `in_file` and `expected_out`, script will execute CMD with `in_file` as stdin and store it's stdout.\n    Finally, it will compare `expected_out` to stdout of the CMD.\n    The output from diff is revealed to the user, unless `fail_text` is provided.\n\n    Option `-c` makes output case sensitive.\n    Option `-s` makes output space sensitive. There needs to be space between words, but amount doesn't matter.\n    Option `-S` makes diff totally ignore space (removes all space before comparison).\n\n    By default, `ok` is printed when the output matches the expected.\n    The string can be changed to a custom value with `-p` or to nothing with `-P`.\n\n    This command can be used with `capture` and `testcase`.\n    E.g. `capture pre stdio-diff in.txt out.txt ./student_code`.\n\n* `create-test-feedback`\n\n    Combines feedback items from `/feedback/` directories to `/feedback/out`.\n    This is automatically executed by `grade` if preconditions apply.\n\n* `err-to-out`\n\n    Appends the `/feedback/err` to `/feedback/out` without `alert-danger` class.\n    Useful for unit test frameworks that produce the feedback into stderr.\n\n* `force-charset CHARSET`\n\n    Converts recursively all files in working directory from any recognizable\n    charsets into desired charset, e.g. utf-8. Discards unconvertible characters.\n    May be useful to sanitize output from exotic student environments.\n\n* `set-error [msg]`\n\n    Sets submission error state by writing `true` to `/feedback/submission-set-error`.\n    If `msg` is provided, then it is written as the reason to `/feedback/grading-script-errors`.\n\n* [chpst](http://smarden.org/runit/chpst.8.html), [setuidgid](https://cr.yp.to/daemontools/setuidgid.html), [softlimit](https://cr.yp.to/daemontools/softlimit.html) and [setlock](https://cr.yp.to/daemontools/setlock.html)\n\n    These utilities are used internally, but can also benefit when writing grading scripts.\n    First one provides the other three.\n    Read linked documentations for more details.\n\n* [envsubst](http://man7.org/linux/man-pages/man1/envsubst.1.html)\n\n    Substitutes environment variables in shell format strings.\n\n    An example usage:\n\n    ```sh\n    $ echo 'My $COLOR dog is huge.' | COLOR=brown envsubst '$COLOR'\n    My brown dog is huge.\n    ```\n\n* [time](http://man7.org/linux/man-pages/man1/time.1.html)\n\n    Utility to measure statistics about timings (e.g. CPU usage).\n\n* [timeout](http://man7.org/linux/man-pages/man1/timeout.1.html)\n\n    Utility command to set wallclock timeouts for commands.\n    You can use this to make sure a test fails after some timeout,\n    so you can run second test before container is killed.\n\n* `gitlab-api-query [-u git_url | -U git_url_file] TESTS.. GIT_HOST [api_token] [require_fork]`\n\n    Checks information in GitLab API (v4) at the given host for given `git_url`.\n    If no `git_url` is provided, then it is read from `git_url_file`.\n    Default for `git_url_file` is `/submission/user/gitsource`, which is created by mooc-grader `types.stdasync.acceptGitAddress` for example,\n    The `git_url` should end with `username/repo` or `username/repo.git`.\n\n    GitLab API often requires authentication and a api token should be set in `api_token`.\n    If the parameter starts with `.` or `/`, then it is expected to be a file containing the token.\n\n    Supported tests:\n\n    * `-p`: require that the project visibility is set to private.\n    * `-f forked_repo`: require that the project is a fork from `forked_repo` (e.g. `username/upstream_repo`).\n\n    Command exists with non zero if no tests are provided.\n\n* `git-clone-submission PRIVATE_KEY_PATH [file paths...]`\n\n    Clones repository from URL submitted as `gitsource` file\n    into /submission/user-repo. The private ssh key allows\n    access to repositories where the public key pair is added\n    as a deploy key. Prints status and exits non zero if fails.\n\n    * file paths...\n\n        List of expected files to check inside the repository.\n        The files are moved into /submission/user and the\n        contents are written as appendix to end of feedback.\n\n\n# Utility commands for grading image Dockerfiles\n\n* `apt_install `\n\n    Calls apt-get update and apt-get install with list of packages.\n    Takes care of correct options and cleaning temporary files in the end.\n","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",148703575,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_50":133,"_134":94,"_135":33,"_136":56,"_57":137,"_138":139,"_140":127,"_141":133,"_142":66,"_143":21},"content_type","creator",10602181,"digest","sha256:7ba5fc6637748f6ad63dcd484e678c47866d376f919be7f2ea4cc983a6b9fda7","full_size",60410340,"id",461187519,"images",[103,118,124,130],{"_104":105,"_95":106,"_107":48,"_108":109,"_110":111,"_112":113,"_114":48,"_115":-5,"_116":98,"_63":66,"_117":-5},"architecture","amd64","sha256:cf6e7a0a69f719a01a3a23e12309fb64b5bd93c13a710e6fff2123d146604275","features","last_pulled","2026-10-01T07:58:16.041279704Z","last_pushed","2023-06-21T11:50:55Z","os","linux","os_features","os_version","size","variant",{"_104":119,"_95":120,"_107":48,"_108":121,"_110":111,"_112":113,"_114":48,"_115":-5,"_116":122,"_63":123,"_117":-5},"arm64","sha256:7df51ca35632fd7bc75903cd59c342318f11509d9b0442ff83e69b3864cb3716","2026-07-29T22:56:30.250383307Z",59076165,"inactive",{"_104":125,"_95":126,"_107":48,"_108":127,"_110":128,"_112":125,"_114":48,"_115":-5,"_116":129,"_63":66,"_117":-5},"unknown","sha256:0e78ec8cf4511801ad9ccb6fcce9cb15696639492617b98ebc9d208bfe1b10a1","2026-10-01T07:58:20.201912277Z","2023-06-21T11:50:54Z",1139,{"_104":125,"_95":131,"_107":48,"_108":132,"_110":111,"_112":125,"_114":48,"_115":-5,"_116":129,"_63":123,"_117":-5},"sha256:9f0f33ed16afd72264d82350e4012e49ccd5fc983e78dd8f12b31296bc8f2a1b","2026-07-29T22:56:30.254097915Z","2023-06-21T11:50:54.940153Z","last_updater","last_updater_username","media_type","latest","repository",20317894,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":157,"_164":165,"_151":177,"_178":11},{"_40":158,"_42":159,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":160,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":161,"_79":11,"_80":163,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":162},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_166":64,"_167":-5,"_168":-5,"_169":170},"count","next","previous","results",[171],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_101":172,"_50":133,"_134":94,"_135":33,"_136":56,"_57":137,"_138":139,"_140":127,"_141":133,"_142":66,"_143":21},[173,174,175,176],{"_104":105,"_95":106,"_107":48,"_108":109,"_110":111,"_112":113,"_114":48,"_115":-5,"_116":98,"_63":66,"_117":-5},{"_104":119,"_95":120,"_107":48,"_108":121,"_110":111,"_112":113,"_114":48,"_115":-5,"_116":122,"_63":123,"_117":-5},{"_104":125,"_95":126,"_107":48,"_108":127,"_110":128,"_112":125,"_114":48,"_115":-5,"_116":129,"_63":66,"_117":-5},{"_104":125,"_95":131,"_107":48,"_108":132,"_110":111,"_112":125,"_114":48,"_115":-5,"_116":129,"_63":123,"_117":-5},[],"canDeleteTags","actionData","errors"]

Digest	OS/ARCH	Compressed size
cf6e7a0a69f7	linux/amd64	57.61 MB
7df51ca35632	linux/arm64	56.34 MB

ihalaij1/grading-base

Tags for ihalaij1/grading-base