Unable to upgrade Bitbucket in Docker Image.
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Attempting to upgrade Bitbucket in a Docker image, you receive an error tÜnable to start the plugin container."
Environment
Docker
Diagnosis
Attempting to upgrade Bitbucket in a Docker image and you receive the following error:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
ERROR [ThreadPoolAsyncTaskExecutor::Thread 1] c.a.plugin.osgi.factory.OsgiPlugin Unable to start the plugin container for plugin 'com.atlassian.support.stp'
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'action-factory' defined in URL [bundle://117.0:0/META-INF/spring/atlassian-plugins-components.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.support.tools.action.impl.DefaultSupportActionFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: Illegal version b11
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:279)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:866)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.lang.Thread.run(Thread.java:748)
... 10 frames trimmed
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.support.tools.action.impl.DefaultSupportActionFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: Illegal version b11
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
... 9 common frames omitted
Caused by: java.lang.IllegalArgumentException: Illegal version b11
at com.atlassian.support.tools.spi.Version.of(Version.java:46)
at com.atlassian.support.tools.action.impl.DefaultSupportActionFactory.<init>(DefaultSupportActionFactory.java:32)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142)
... 9 common frames omitted
Cause
The BUILD_VERSION in your Docker image is set as your Java container build variable and is being picked up by Bitbucket, which causes it to fail.
Solution
Change the variable name from BUILD_VERSION to JAVA_BUILD_VERSION or something similar for your Java variable.
Was this helpful?