Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Fabric8io docker-maven plugin runs on pipeline only from inside a bash script Edited

We use the fabric8io docker-maven plugin to manage docker image building within our project, and while it runs fine locally when we use it on Pipelines we get the following:

Downloaded from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/23.0-android/guava-23.0-android.jar (2.5 MB at 2.4 MB/s)
[ERROR] DOCKER> Cannot create docker access object [Connect to localhost:2375 [localhost/127.0.0.1] failed: Connection refused (Connection refused)]

[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.31.0:build (default-cli) on project parent: Cannot create docker access object : Connect to localhost:2375 [localhost/127.0.0.1] failed: Connection refused (Connection refused) -> [Help 1]

 However, we *only* get that error if we use the plugin directly, ie by including a step of:

    mvn docker:build

If we have the same command inside a bash script and get Pipelines to call the bash script as a step, the plugin build succeeds.

I've tried looking at env both as a step and inside the bash script to compare, and in both cases the only difference is sub-shell layer. Running env also appears to cause the plugin to start failing even from inside a bash script.

Any thoughts?

 

Edit: Since the env tests, that branch (and only that branch) is now failing even if the plugin is called from inside a script.

1 answer

Okay folks, I'm an eejit - it helps if one remembers that the reason it worked from the bash script on one step was because that was the one where you had the Docker service set up...!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

141 views 1 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you