{{ message }}
Repository navigation
feat(runtime): push monorepo Actors to the local Actor runtime - #1470
Merged
Merged
Conversation
…ctor runtime apify push of an Actor whose .actor/actor.json sets dockerContextDir now pushes the whole Docker context to the local Actor runtime, with the Actor's folder inside it and the Git branch/commit of the working copy, and registers the context root as the dev folder. Against the Apify platform, such a push stops with an error pointing to https://github.com/apify/apify-core/issues/28685. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YLTcFYmvHYZwuwLdHDphTQ
…repo files Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YLTcFYmvHYZwuwLdHDphTQ
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YLTcFYmvHYZwuwLdHDphTQ
- files in the Actor's folder follow its own .actorignore (force-includes too), exactly as an ordinary push of that folder - the context is pushed before an existing version is updated, and a newly created version is removed again when the push fails, so a refused push changes nothing - the uncommitted-changes flag covers only the pushed Docker context - clearer message for a runtime without the endpoint; no size sum or buffer copy for context pushes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YLTcFYmvHYZwuwLdHDphTQ
- the files are those Git tracks, as on disk, plus untracked files it does not ignore; .actorignore does not apply, as it does not to the platform's Git builds - a dockerContextDir outside the Git repository is rejected, since the platform could not build it; uncommitted changes are pushed with a warning - files keep their permission bits in the pushed archive Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YLTcFYmvHYZwuwLdHDphTQ
The runtime now takes the Docker context from the pushed files as the platform's builder does, so apify push sends the Git repository's root with the Actor's path inside it (the context root outside Git), and keeps symlinks as links. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YLTcFYmvHYZwuwLdHDphTQ
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YLTcFYmvHYZwuwLdHDphTQ
Pijukatel
added a commit
to apify/actor-runtime
that referenced
this pull request
Sep 30, 2026
- Monorepo Actors (`dockerContextDir` in `.actor/actor.json`) can be pushed and built: `PUT /actor-runtime/source-context/:actorId/:versionNumber` takes the repository as one `.tar.gz`, plus the Actor's folder in it. - Every build now takes its Docker context as the platform's builder (apify-worker) does: context from `dockerContextDir` inside the pushed files, schema paths anywhere in them, Dockerfile only from the context, files `0777`, symlinks kept. - `ACTOR_PATH_IN_DOCKER_CONTEXT` is passed to every build, and env vars override it; a named `input` file that does not exist fails the build. - New `samples/actor_monorepo` and e2e tests covering builds that fail and succeed as they would from Git on the platform; the e2e runs only with a local CLI until apify/apify-cli#1470 is released. --------- Co-authored-by: Claude <noreply@anthropic.com>
Pijukatel
marked this pull request as ready for review
September 30, 2026 13:17
Pijukatel
requested review from
DaveHanns,
l2ysho and
szaganek
as code owners
September 30, 2026 13:17
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
apify pushof an Actor whose.actor/actor.jsonsetsdockerContextDirsends its Git repository, as the platform's clone would have it, to the local Actor runtime (feat: Add support for monorepo Actors with shared Docker contexts actor-runtime#89), with the Actor's path in it..actorignore; uncommitted changes are pushed with a warning.dockerContextDiroutside the Git repository is rejected; the Docker context is registered as the dev folder.archiver).