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

Test Automation Using docker.bintray.io/jfrog/artifactory-oss Image #187

Open
faraonc opened this issue Jan 30, 2020 · 3 comments
Open

Test Automation Using docker.bintray.io/jfrog/artifactory-oss Image #187

faraonc opened this issue Jan 30, 2020 · 3 comments

Comments

@faraonc
Copy link

faraonc commented Jan 30, 2020

I am writing a script to automate grooming our Artifactory. Due to some of the files are currently used for production, I want to test my script using docker.bintray.io/jfrog/artifactory-oss image. Is there a way to prevent Artifactory to force user admin to change password on initial startup?

Thanks!

@jamshid
Copy link

jamshid commented Feb 10, 2020

Yeah docker.bintray.io/jfrog/artifactory-oss:4.16.1 was nice because it would automatically be configured for anonymous access and with a maven repo. Now with 6.17.0 I have to manually go to the http://DOCKER-HOST:8081 website and login initially as admin:password, change password to a long password, skip proxy server, Create the Maven repo, then go to Admin => Security Configuration => Allow anonymous.

@eldada
Copy link
Contributor

eldada commented Feb 26, 2020

@faraonc This is a general change for Artifactory. Not related to the Docker image.
Can you open an issue in Artifactory's public JIRA?

@faraonc
Copy link
Author

faraonc commented Mar 9, 2020

@faraonc This is a general change for Artifactory. Not related to the Docker image.
Can you open an issue in Artifactory's public JIRA?

@eldada
I think we pretty much abandon the test, so I am gonna let you determine if writing a JIRA ticket is still needed.

It is important to note that most Docker images available like Postgres or MongoDB would have an entrypoint directory available to initialize the container in the proper state.

For example:
Note: - ./db/postgres/sql_scripts/:/docker-entrypoint-initdb.d

    postgres:
        image: postgres:12.1
        container_name: postgres
        command: -c ssl=on -c ssl_cert_file=/var/lib/postgresql/cert.pem -c ssl_key_file=/var/lib/postgresql/key.pem
        ports:
            - "${FS_PG_PORT:-5432}:${FS_PG_PORT:-5432}"
        environment:
            POSTGRES_USER: ${FS_PG_USER:-pgadmin}
            POSTGRES_PASSWORD: ${FS_PG_PWD:-pgpwd}
        volumes:
            - ./db/postgres/sql_scripts/:/docker-entrypoint-initdb.d
            - ./ca/cert.pem:/var/lib/postgresql/cert.pem
            - ./ca/key.pem:/var/lib/postgresql/key.pem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants