# \#forge-containers **URL:** https://community.developer.atlassian.com/tag/forge-containers/1655.md [Latest](https://community.developer.atlassian.com/latest.md) · [Categories](https://community.developer.atlassian.com/categories.md) · [Tags](https://community.developer.atlassian.com/tags.md) --- ## [Forge has started leaving unexpected folders in our local git clone](https://community.developer.atlassian.com/t/forge-has-started-leaving-unexpected-folders-in-our-local-git-clone/102656)
**Author:** [@scottohara](https://community.developer.atlassian.com/u/scottohara)\ **Replies:** 4\ **Last updated:** [October 12, 2026, 8:03am UTC](https://community.developer.atlassian.com/t/forge-has-started-leaving-unexpected-folders-in-our-local-git-clone/102656 "2026-10-12T08:03:13Z")
Hi @HeyJoe , With reference to this post about Forge Container Services preview, we are not currently evaluating this ourselves, but we did recently upgrade our app to use the latest @forge/\* npm packages and we noticed… --- ## [Forge Containers: invokeService requires 'body: string'?](https://community.developer.atlassian.com/t/forge-containers-invokeservice-requires-body-string/103033)
**Author:** [@RomanStoffel](https://community.developer.atlassian.com/u/RomanStoffel)\ **Replies:** 4\ **Last updated:** [October 12, 2026, 8:01am UTC](https://community.developer.atlassian.com/t/forge-containers-invokeservice-requires-body-string/103033 "2026-10-12T08:01:19Z")
For the Forge Containers the ‘invokeService’, the body argument has a type ‘unknown’, and the documentation states that it must be a JSON. This aligns with other similar calls, like invokeRemove However, in practise it… --- ## [Forge container deployment failed for development environment](https://community.developer.atlassian.com/t/forge-container-deployment-failed-for-development-environment/102064)
**Author:** [@AlexandraIvanova](https://community.developer.atlassian.com/u/AlexandraIvanova)\ **Replies:** 9\ **Last updated:** [October 2, 2026, 2:21pm UTC](https://community.developer.atlassian.com/t/forge-container-deployment-failed-for-development-environment/102064 "2026-10-02T14:21:44Z")
Hello, My Forge container unexpectedly stopped deploying for my forge app (App ID: f8448394-3126-4070-8dbb-8f4a8ad94bed). Unfortunately, there are no additional logs available. I’m running: forge deploy -e development… --- ## [Forge container services are now in Preview](https://community.developer.atlassian.com/t/forge-container-services-are-now-in-preview/102053)
**Author:** [@HeyJoe](https://community.developer.atlassian.com/u/HeyJoe)\ **Replies:** 5\ **Last updated:** [August 12, 2026, 11:48am UTC](https://community.developer.atlassian.com/t/forge-container-services-are-now-in-preview/102053 "2026-08-12T11:48:20Z")
We’re excited to share that Forge container services is now in Preview. Apps using container services can now be deployed to production environments, published on the Atlassian Marketplace, and distributed to customers.… --- ## [RFC-138: Move fields out of invocation context to address header size limits for Forge Remote and Forge Containers](https://community.developer.atlassian.com/t/rfc-138-move-fields-out-of-invocation-context-to-address-header-size-limits-for-forge-remote-and-forge-containers/101344)
**Author:** [@LauraHowarthKirke](https://community.developer.atlassian.com/u/LauraHowarthKirke)\ **Replies:** 20\ **Last updated:** [August 10, 2026, 2:25pm UTC](https://community.developer.atlassian.com/t/rfc-138-move-fields-out-of-invocation-context-to-address-header-size-limits-for-forge-remote-and-forge-containers/101344 "2026-08-10T14:25:14Z")
Hi everyone, Project Summary Publish: 19 June 2026 Discuss: 17 July 2026 Resolve: 30 July 2026 We’re proposing a reduction of the fields included in the signed invocation context sent to Forge Remotes and Forge Conta… --- ## [Migrating a Connect + Spring Boot app to Forge Remote (and Containers) without rewriting your service layer](https://community.developer.atlassian.com/t/migrating-a-connect-spring-boot-app-to-forge-remote-and-containers-without-rewriting-your-service-layer/100846)
**Author:** [@vzakharchenko](https://community.developer.atlassian.com/u/vzakharchenko)\ **Replies:** 2\ **Last updated:** [May 21, 2026, 2:49pm UTC](https://community.developer.atlassian.com/t/migrating-a-connect-spring-boot-app-to-forge-remote-and-containers-without-rewriting-your-service-layer/100846 "2026-05-21T14:49:43Z")
Hi everyone, If you still run a Connect add-on on Spring Boot and need to move to Forge Remote, the usual fear is a full rewrite: new auth model, new Jira clients, new tenant keys, new UI, new manifest — all at once. T… --- ## [Debugging Forge Containers locally (Java + IntelliJ + Spring Boot)](https://community.developer.atlassian.com/t/debugging-forge-containers-locally-java-intellij-spring-boot/99921)
**Author:** [@vzakharchenko](https://community.developer.atlassian.com/u/vzakharchenko)\ **Replies:** 1\ **Last updated:** [April 15, 2026, 12:54pm UTC](https://community.developer.atlassian.com/t/debugging-forge-containers-locally-java-intellij-spring-boot/99921 "2026-04-15T12:54:35Z")
Atlassian’s documentation for local Forge Containers testing describes two supported ways to run a service locally: using the tunnel.docker configuration in manifest.yml, or setting up the Docker Compose stack manually a…