You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there anyway to build and use a container without intermediate storage outside the runner/job?.
I have a docker file that would be great to run, and if its container.image that is exactly what I want, but it needs to be built first.
Which puts in the awkward situation of publishing to a different registry, for something that lives along as the job needs to, and the complicated moving parts of setting up something to publish and then consume it.
The other option, is taking the base of my docker file, and then recreating all the steps in the dockerfile to end up with an environment that's similar. It works, but it's a bit awkward to have to duplicate my docker file, when I am already running in a container.
This may exist, and I am just not seeing it in the documentation, but a bit confused that container for a job exists, but doesn't seem straightforward to have a docker file for.
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestion
2 participants
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
Is there anyway to build and use a container without intermediate storage outside the runner/job?.
I have a docker file that would be great to run, and if its container.image that is exactly what I want, but it needs to be built first.
Which puts in the awkward situation of publishing to a different registry, for something that lives along as the job needs to, and the complicated moving parts of setting up something to publish and then consume it.
The other option, is taking the base of my docker file, and then recreating all the steps in the dockerfile to end up with an environment that's similar. It works, but it's a bit awkward to have to duplicate my docker file, when I am already running in a container.
This may exist, and I am just not seeing it in the documentation, but a bit confused that container for a job exists, but doesn't seem straightforward to have a docker file for.
Beta Was this translation helpful? Give feedback.
All reactions