-
Notifications
You must be signed in to change notification settings - Fork 119
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
Allow disabling of SSL redirection #21
Conversation
Apologies for delay, and thank you in advance for your efforts. Updated docker-compose.yml with your changes, but trying to determine how to pull the noredirect build. Can you provide a hint on the convention of how to specify a specific build within the Docker-Compose.yml? I have tried various sub-tags, and tried fudging the image location, but gave up after about an hour. misp-core: |
This is exactly what I needed. Hope this will get merged soon 👍🏼 |
@gritty-Kitty , you need to build the image first, then just use the tag @kelke only after there is some testing, so any help is appreciated in that direction :) |
Good afternoon, I have attempted a build, but have stalled. Any insight on how to resolve is greatly appreciated. Had to edit Dockerfile CORE_TAG=2.4 so it would resolve and compile. infinity@ONHMISP0ZWF001: infinity@ONHMISP0ZWF001:~/misp-docker-noredirect/core$ sudo docker build -t misp-core . |
You need to create the |
Good morning, Our implementation is based on Ubuntu 22.04 LTS, Docker, and Portainer. I appear to lack the knowledge and experience required to compile and test. I struggled with Docker at the command line with a .env file that did not appear to be recognized (same output as above). https://stackoverflow.com/questions/47968875/how-to-build-docker-with-env-file Then turned my focus towards building an Image in Portainer, but it also exhibited errors during the build process. There does not appear to be any mechanism that allows me to bind a .env file to the Portainer Image creation process. |
The error you are seeing is because of an old version of docker (or docker-compose). |
Good afternoon, The server is a new build (~2-weeks old) using Microsoft Azure Marketplace Ubuntu 22.04 LTS with all updates/upgrades applied weekly. The sole purpose of this server is to host MISP, but due to aging dependencies, we were forced to entertain a Docker-instance, and found your project. Docker was pulled using apt-get, and Portainer was pulled from Docker when installed. Posted here for your awareness. sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose Can't comment on age or freshness of Docker or Docker-Compose, other than this was a fresh installation. My build efforts revolved around the DockerFile and creating a new Image so I could return to my Portainer Stack and attempt a redeployment, but could never get the build to work. Apologies in advance. I tried. |
I've just merged it. |
I did not find any bugs as well. Works just as expected |
No description provided.