Skip to content

Conversation

@dalanlan
Copy link
Contributor

part of #12151
remove job from image_export
Signed-off-by: Simei He hesimei@zju.edu.cn

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this trick really necessary here? I think it will be enough just return error. At least it'll preserve old behavior.

graph/export.go Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll totally remove this line since it's not a job anymore, or maybe write another message

Signed-off-by: Simei He <hesimei@zju.edu.cn>

Signed-off-by: He Simei <hesimei@zju.edu.cn>
@dalanlan dalanlan force-pushed the remove_job_from_image_export branch from 5122621 to 30557fc Compare April 23, 2015 11:05
@runcom
Copy link
Member

runcom commented Apr 23, 2015

thanks @dalanlan

@dalanlan
Copy link
Contributor Author

@duglin @LK4D4 Updated:)
@runcom thx too:)

@runcom
Copy link
Member

runcom commented Apr 23, 2015

looks ok to me apart from that engine needed in exportImage

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why we just don't return error here? I'm pretty sure that you're not returning JSONError from ImageExport.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I got it. But we're not doing Used trick then?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is superweird. You should write json-error directly to w if error encountered after Flushed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's the NEW legacy of postImagesCreate.
i thought u guys were not pleasant with Flushed or Used stuff and somehow i was not able to make binary locally due to network problem so i just corrected it in your way:(
I would write a pr to correct postImagesCreate then since it is also weird when you type docker pull scratch or sth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants