Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offline Environment Error: Unable to Pull Mongo Image in Porter v1.1.0 #3198

Closed
jmcudd opened this issue Jul 31, 2024 · 4 comments · Fixed by #3210
Closed

Offline Environment Error: Unable to Pull Mongo Image in Porter v1.1.0 #3198

jmcudd opened this issue Jul 31, 2024 · 4 comments · Fixed by #3210
Labels
bug Oops, sorry!

Comments

@jmcudd
Copy link
Contributor

jmcudd commented Jul 31, 2024

Describe the bug

When using Porter in an offline environment, it attempts to pull the mongo:4.0-xenial image, resulting in an error due to the lack of internet connectivity. This prevents the successful execution of Porter commands that rely on this image.

To Reproduce

Steps to reproduce the behavior:

  1. Install the Porter binary in an offline environment.
  2. Run the command porter list.
  3. See the error message regarding the inability to pull the mongo:4.0-xenial image.

Expected behavior

I expected the porter list command to execute successfully and list the installations without attempting to pull any external dependencies, as the environment is offline.

Porter Command and Output

$ porter list
rpc error: code = Unknown desc = error pulling mongo:4.0-xenial: 
could not list installations: could not read storage schema document: rpc error: code = Unknown desc = error pulling mongo:4.0-xenial: 
could not list installations: could not read storage schema document: rpc error: code = Unknown desc = error pulling mongo:4.0-xenial:

Version

porter v1.1.0
@jmcudd jmcudd added the bug Oops, sorry! label Jul 31, 2024
@kichristensen
Copy link
Contributor

@sgettys I seem to remember you talking about this some time ago. What was the output of that? Can't remember

@jmcudd
Copy link
Contributor Author

jmcudd commented Aug 1, 2024

I also experience it with porter install.

Looking at the documentation there is mention of mongo in the Porter Config File, but its not clear to me what else it can be set to.

I also tried pulling the mongo:4.0-xenial image into my environment and loading it into docker and that had no effect.

@jmcudd
Copy link
Contributor Author

jmcudd commented Aug 1, 2024

I found some more useful docs here. Looks like I may be able to just run mongo and connect to it by updating my porter config.

@jmcudd
Copy link
Contributor Author

jmcudd commented Aug 1, 2024

I believe I've come up with a work-around. This obviously doesn't solve all the other offline issues like mixins, but it does appear as though the exec mixin works out of the box.

Steps:

  1. Download mongo:4.0-xenial
  2. Run Mongo in docker with the name: porter-mongodb-docker-plugin and port 27018
docker run --name porter-mongodb-docker-plugin -d -p 27018:27017 -v mongodb_data:/data/db --restart always mongo:4.0-xenial

Result:

$ porter list
------------------------------------------------------------
  NAMESPACE  NAME  VERSION  STATE    STATUS  MODIFIED       
------------------------------------------------------------

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Oops, sorry!
Projects
None yet
2 participants